{"title":"Bugzilla Blog","subtitle":"The software solution designed to drive software development, which lets you plan, organize and release software on your own teams' schedule.","icon":"\/assets\/favicon\/favicon.png","logo":"\/assets\/favicon\/favicon.png","link":[{"@attributes":{"href":"https:\/\/www.bugzilla.org\/blog"}},{"@attributes":{"href":"https:\/\/www.bugzilla.org\/blog\/atom.xml","rel":"self","type":"application\/atom+xml"}},{"@attributes":{"href":"https:\/\/www.bugzilla.org\/blog","rel":"alternate"}}],"updated":"2026-03-20T17:22:43+00:00","id":"https:\/\/www.bugzilla.org\/blog\/atom.xml","generator":"Jekyll","author":{"name":"Bugzilla Webmasters","email":"webmaster@bugzilla.org"},"entry":[{"id":"https:\/\/www.bugzilla.org\/blog\/2024\/09\/03\/release-of-bugzilla-5.2-5.0.4.1-and-4.4.14\/","author":{"name":"Dave Miller","uri":"https:\/\/www.bugzilla.org\/about\/developers\/justdave\/"},"published":"2024-09-03T00:00:00+00:00","updated":"2026-03-20T17:22:43+00:00","title":"Release of Bugzilla 5.2, 5.0.4.1, and 4.4.14","link":{"@attributes":{"href":"https:\/\/www.bugzilla.org\/blog\/2024\/09\/03\/release-of-bugzilla-5.2-5.0.4.1-and-4.4.14\/"}},"content":"

posted by Dave Miller<\/a> - Bugzilla Project Lead<\/em><\/p>

This has been a long<\/strong> time coming. Just over a year since we announced the new nonprofit to manage Bugzilla<\/a>, we finally have a set of releases to show for it. Our only excuse is that the lead developer is a volunteer, has been working almost (but not quite) alone on it, and still has to juggle his normal paying job. A little more about what can be done about that below. First let\u2019s get to the big news!<\/p>

The Releases<\/strong><\/h2>

Here\u2019s what we\u2019re releasing today:<\/p>

4.4.14<\/strong> \u2013 The 4.4 branch has been on life support for a LONG<\/strong> time (it was initially released in 2013!!!<\/strong>). It supports outdated OSes that are hard to find or install, let alone test for these days, and we\u2019ve been itching to drop it for a long time.\u00a0 But our support policy says that we have to support it for 4 months after the following two major releases.\u00a0 The next major release after 4.4 was 5.0, and there have been no major releases after that until today. That four month countdown to End-of-Life starts NOW.<\/strong> This will be the final release of the 4.4 branch (barring any additional security issues being found in the next 4 months).<\/p>

5.0.4.1<\/strong> \u2013 Why 5.0.4.1 when there\u2019s a 5.0.6 release?\u00a0 Well, if you paid attention to the change logs, 5.0.5 and 5.0.6 contained a massive schema change, as well as reformatting almost all of the Perl code in the source, both of which are a violation of our support policy for a stable branch (a new-to-the-process release manager pushed the release out not realizing that, and by the time we caught it, it was too late). A lot of people noticed this and never upgraded to 5.0.5 or 5.0.6, since they didn\u2019t contain any security fixes.\u00a0 5.0.4.1 will give those people additional fixes for 5.0.4 without forcing them to pick up those schema and code reformatting changes. Additional updates to the 5.0 branch from now on will continue from 5.0.4.2 and onward.<\/p>

5.2<\/strong> \u2013 This is our new stable release, and starts the 4 month countdown for discontinuing the 4.4 branch. 5.2 is forked from the 5.0 branch after 5.0.6, and will contain those schema and code formatting changes from 5.0.5 and 5.0.6 in it. So if you did<\/strong><\/em> upgrade to 5.0.6, 5.2 will be equivalent to a point upgrade for you.\u00a0 Those schema changes should have caused a major release to happen anyway, so this is just fixing the numbering problem with that release (i.e. 5.0.5 should have been called 5.2 to begin with). Note that if you are using the 5.1.x development releases, those did NOT feed into this<\/strong>, and 5.2 would actually be a downgrade for you.<\/p>

5.3.3<\/strong> \u2013 In order to avoid confusion with 5.2 above, the 5.1 branch has been retroactively renumbered to 5.3. It is also basically dead, as we\u2019ve put all of our resources into finishing off the Harmony release (see 5.9.1 below). We\u2019re going to encourage people on 5.1.x\/5.3.x to move to Harmony, but you\u2019ll want to be mindful of the release blockers first before you make the jump. There are some features in 5.1.x\/5.3.x that were implemented differently in Harmony, and the code to migrate the related data may or may not work yet (if the feature in question is listed on the release blockers and you use it, you\u2019ll want to wait for now). Even though this branch is dead, we\u2019re put out this release with the current batch of security fixes so you aren\u2019t left high and dry before Harmony is ready for you.<\/p>

5.9.1<\/strong> \u2013 This is the first official release off the Harmony branch, and is classified as a developer preview release<\/strong>, not for production use. This is what will eventually be Bugzilla 6.\u00a0The code is mostly good enough to use right now, but there are still showstoppers to be able to fully release it as a production release. There are also a few gotchas when upgrading from older versions of Bugzilla. If you\u2019re interested in helping make Bugzilla 6 happen, that list of showstoppers is here<\/a>. We are hoping to have Bugzilla 6 in release candidate stage (or at least in beta) within the next few months.<\/p>

Download<\/h2>

Bugzilla is available at:<\/p>

https:\/\/www.bugzilla.org\/download\/<\/a><\/p>

Release Notes & Changes<\/h2>

Before installing or upgrading, you should read the Release Notes for this version of Bugzilla:<\/p>