1.7 Release Plan
From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Wed, 28 Jul 2010 16:56:21 -0500
This is a draft of the release plan for 1.7. I figure it's important
---- Beta releases improve upon the general stability of alpha releases, and contain protocols and APIs which are considered to be "finalized". Beta releases are tested and signed, but may also contain known issues, hopefully fewer than alpha releases. Any issues are summarized in the release announcement. Signing policies are similar to that of alpha releases. Release Candidate ----------------- Release candidates are just that: candidates for a final release. They are tested and signed, and should contain no known issues of sufficient severity. Should no serious bugs be found during testing, a release candidate will become the final release. Final or Generally Available (GA) --------------------------------- The tarball which is released to the world as Subversion. Tested, signed and blessed by the community for wide-spread consumption. As stable as we can get it. Timeline ======== None of the following actions have dates corresponding to them. Instead, we can progress between stages as dictated by the results of the previous stage, as well as the consensus of the community. (The notable exception is the customary 28-day minimum soak period during the release candidate stage.) Full release process details are available here: http://subversion.apache.org/docs/community-guide/releasing.html Events ------ Stabilize on-disk formats Start publishing frequent alpha releases Review APIs, protocols Start publishing frequent beta releases Branch 1.7.x Publish first RC / start soak Publish interim RCs, restarting soak as needed Publish final RC Publish Subversion 1.7.0 It looks like we might be fairly close to having on-disk formats stabilized, and hence rolling alphas. Prereleases may be fairly prolific, since I want to work the bugs out of the transition to ASF distribution infrastructure, and get fixes into the hands of users rapidly. If you've got comments or questions, let's hear 'em! -Hyrum  Of course, we reserve the right to change disk formats and APIs prior to the generally available release, and will include said caveat in the release announcements. The benefit of this guideline is having at least some sort of user and developer expectation.  No software is bug-free, and we will almost certainly have to make the painful choice between releasing soon with a bug, or releasing later with a bug-fix. The definition of "sufficient severity" is left as an exercise for the PMC.Received on 2010-07-28 23:57:01 CEST
This is an archived mail posted to the Subversion Dev mailing list.