On Mon, May 02, 2005 at 03:49:25PM -0700, Dan Quinlan wrote: > http://wiki.apache.org/spamassassin/ReleasePolicy > > I have attempted to clarify some of the release process and also beefed > up the build/README (thanks Michael for some input on these).
-1 The current documentation contradicts itself in several places. For instance: "Note that no one may veto a release. The PMC or the release manager may revoke all votes on a release if a new major problem is discovered prior to publication of a release and request a revote. However, once there are greater than 3 positive votes, the release may be made at any time. In addition, the RM may decide against making a release even if the required votes have been made." 1) It says that no one may veto a release, and then it goes on to say that the RM may veto a release. If no one can veto, then no one can veto. 2) "... once there are greater than 3 positive votes ..." So that's 4 votes for a release. I'm fine with that, but everywhere else it says 3. "If the "point of no return" described in the build/README has not been reached, then the release may be abandoned and begun again." 3) There is no easily identifiable "point of no return" in build/README. Is it the release prep commit, the tree tag, the tarball build, the "x.y.z released" commit? I'd say if we go with the "version burned" approach, it's the tree tag stage. Whichever it is, we should make it an easily identifiable stage, such as using the phrase "point of no return". ;) I still think there needs to be some general time given so that the people involved know about a release before it happens. We look very foolish as a whole when, say, a PMC member is discussing future releases with third parties, and then it's pointed out by said party that a release just occured which was not known about ahead of time. Should there be any discussion about stable vs development releases and generally what is expected? I'm not hot on the "version number is burned at tarball time" idea (pun intended?) It really does tend to confuse users who wonder why things go X, X+1, X+3, ... This isn't a major issue, but I wanted to share. -- Randomly Generated Tagline: "Hurry up! I wanna see the moon." -Fry "Relax. It's open 'till nine." -Leela
pgpPvWBozKrq1.pgp
Description: PGP signature
