> From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Ulrich Mayring > > Berin Loritsch wrote: > > > > Minor nitpick: > > > > The release was *prevented*. Once a release is made, we > have to support > > it. There is no "oops, I didn't mean to do that". > > The release was up for downloading and then deleted. Just > like a faulty > commit is up for downloading and can be deleted, if a problem > arises. I > don't see the difference, except for that support issue you > brought up. > Curious: what does that support consist of that is given for > a release, > but not for a cvs version?
Support means answering questions regarding the released product and how it works--note the answer should not be "get the latest CVS and ....". It also means that we need to incorporate bug fixes into subsequent releases. It also means that release 4.0.3 should not be wildly different from release 4.0.2. The bottom line is that we are willing to help users of the release. > I'm just trying to understand the procedures here, because I want to > learn something for my own use in other projects. What are the people, > who voted +1 now, committing themselves to, which they wouldn't if it > was just a cvs commit? What is the reasoning behind a +1 or > -1 for a release? 9 times out of 10, a release does not get a -1 unless there is an outstanding technical issue. What is typical in most projects is to create a release archive, put it on the server as a Release Candidate (i.e. Apache httpd-2.1.0rc1), and let the community work with it for a little bit. If there are no real Blockers (a really bad error like "it erased my hard drive when under XYZ circumstances), then the release will be made. There can be several iterations of the Release Candidates--where the *only* difference is a bug fix. During the whole Release Candidate process, the code is considered "frozen". That means that there are no more features being added, and the only thing being considered are bug fixes. The community may feel that a bug is so minor that they can live with it for this release rather than create a new Release Candidate for it. When the release is official, the announcements are made in the general locations. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
