<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Name on rmqa.com</title>
    <link>https://rmqa.com/tags/the-name/</link>
    <description>Recent content in The Name 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/the-name/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why the Release Checker Is Called rmqa</title>
      <link>https://rmqa.com/why-the-release-checker-is-called-rmqa/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/why-the-release-checker-is-called-rmqa/</guid>
      <description>&lt;p&gt;rmqa stands for release manifest QA. Each part of the name is one idea, and together they describe the whole tool.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Release.&lt;/strong&gt; Not the build, not the code, not the pipeline. The release is the set of files people download: the archives, the bare programs, the checksums. It&amp;rsquo;s the one product of a software project that users see directly, and it&amp;rsquo;s assembled at the very end, often by a script that was written once and rarely looked at again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
