<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic FF 106.0.1 for Mac – why does it exist? in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/ff-106-0-1-for-mac-why-does-it-exist/m-p/16696#M7320</link>
    <description>&lt;P&gt;I see there's now Firefox 106.0.1 out. After updating, I go to check out what's new, as always.&lt;/P&gt;&lt;P&gt;The only fix listed says:&lt;/P&gt;&lt;P&gt;"Addresses a crash experienced by users with AMD Zen1 CPUs."&lt;/P&gt;&lt;P&gt;The number of Macs with an AMD processor of any kind is precisely zero.&lt;/P&gt;&lt;P&gt;I even saw a release for Firefox 105 for which the only purpose was to fix a Windows bug – but Mac users still got an update. Before that, I seem to recall one targeted only at Linux – but Mac users got an update anyway.&lt;/P&gt;&lt;P&gt;Does this mean that Mozilla is now in the habit of releasing a new version when &lt;EM&gt;nothing has actually changed&lt;/EM&gt;, just for the sake of version number parity across platforms?&lt;/P&gt;&lt;P&gt;I miss the days when a version number meant something, before the pointless race with Google Chrome began, and a .0 release didn't come every month. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Oct 2022 20:07:11 GMT</pubDate>
    <dc:creator>Sixfold0371</dc:creator>
    <dc:date>2022-10-20T20:07:11Z</dc:date>
    <item>
      <title>FF 106.0.1 for Mac – why does it exist?</title>
      <link>https://connect.mozilla.org/t5/discussions/ff-106-0-1-for-mac-why-does-it-exist/m-p/16696#M7320</link>
      <description>&lt;P&gt;I see there's now Firefox 106.0.1 out. After updating, I go to check out what's new, as always.&lt;/P&gt;&lt;P&gt;The only fix listed says:&lt;/P&gt;&lt;P&gt;"Addresses a crash experienced by users with AMD Zen1 CPUs."&lt;/P&gt;&lt;P&gt;The number of Macs with an AMD processor of any kind is precisely zero.&lt;/P&gt;&lt;P&gt;I even saw a release for Firefox 105 for which the only purpose was to fix a Windows bug – but Mac users still got an update. Before that, I seem to recall one targeted only at Linux – but Mac users got an update anyway.&lt;/P&gt;&lt;P&gt;Does this mean that Mozilla is now in the habit of releasing a new version when &lt;EM&gt;nothing has actually changed&lt;/EM&gt;, just for the sake of version number parity across platforms?&lt;/P&gt;&lt;P&gt;I miss the days when a version number meant something, before the pointless race with Google Chrome began, and a .0 release didn't come every month. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2022 20:07:11 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/ff-106-0-1-for-mac-why-does-it-exist/m-p/16696#M7320</guid>
      <dc:creator>Sixfold0371</dc:creator>
      <dc:date>2022-10-20T20:07:11Z</dc:date>
    </item>
  </channel>
</rss>

