<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Explainers on rmqa.com</title>
    <link>https://rmqa.com/tags/explainers/</link>
    <description>Recent content in Explainers on rmqa.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rmqa.com/tags/explainers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Release Verification Is and Why a Green CI Run Is Not Enough</title>
      <link>https://rmqa.com/what-release-verification-is-and-why-a-green-ci-run-is-not-enough/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/what-release-verification-is-and-why-a-green-ci-run-is-not-enough/</guid>
      <description>&lt;p&gt;Most software teams test their code thoroughly. Unit tests, integration tests, linters, type checks, builds on several operating systems. When all of that passes, the pipeline goes green and the release goes out.&lt;/p&gt;&#xA;&lt;p&gt;But the tests check the code. They don&amp;rsquo;t check the release. And a release isn&amp;rsquo;t code: it&amp;rsquo;s a set of files, assembled at the very end by a few lines of script, that users download and run. Release verification means checking that set of files, as a whole, before it&amp;rsquo;s published.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
