[Rpm-maint] [rpm-software-management/rpm] A break in the regularly scheduled programme (Discussion #4175)

[Panu Matilainen]

After some consideration, we've decided to do an exception to our annual release cycle this year.

RPM 6.0 development ran so deep into last year that there hasn't been much time for new developments since then. 
So instead of releasing RPM 6.1 through the alpha-beta-rc-final cycle across Q2 and Q3, we'll be releasing 6.0.2 with just a release candidate pre-release in this quarter. 

One could say that it's just a number, why bother? The answer is that because of the way RPM uses the major version for the package version, minor version updates can be, and often have been quite disruptive. Here,  we want to signal the strictly non-breaking nature of the release, to which all 6.0 users can safely update to. Hence, 6.0.2.

This maneuver should let us get back on the normal development cycle going forward.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/4175
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/repo-discussions/4175 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20260408/4e6e6d94/attachment-0001.htm>