-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
OK, I do not agree with this. in my opinion, a release number is only "burned in stone" once the file is announced, uploaded to CPAN, etc. I'd prefer to avoid "burning" too early, as it makes for less flexibility. What if a bug is found in those prerelease tarballs? We move onto 3.0.(x+1) without issuing 3.0.x, immediately? That's (a) messy, (b) ugly, (c) will cause confusion among users and packagers, and (d) is unprecedented either in *this project*, or others. Let's not make rules for the sake of making rules! (PS: I think you mean "discreet" (non-public) rather than "discrete" (singular, atomic)) - --j. [EMAIL PROTECTED] writes: > Author: quinlan > Date: Mon May 2 15:30:35 2005 > New Revision: 165704 > > URL: http://svn.apache.org/viewcvs?rev=165704&view=rev > Log: > move the point of return to be a bit earlier > > Modified: > spamassassin/trunk/build/README > > Modified: spamassassin/trunk/build/README > URL: > http://svn.apache.org/viewcvs/spamassassin/trunk/build/README?rev=165704&r1=165703&r2=165704&view=diff > =============================================================================--- > spamassassin/trunk/build/README (original) > +++ spamassassin/trunk/build/README Mon May 2 15:30:35 2005 > @@ -127,6 +127,11 @@ > > svn commit -m "X.Y.Z RELEASED" > > + this is the point of no-return, once this commit has been made, the > + version number is considered "burned". Even if the release is not > + made at this point, the number is locked for this particular code. > + The same number cannot be used for a future different release. > + > - Now, start the new development codebase. For minor updates of a 2.x > tree (e.g. 2.x1, 2.x2), you don't need to branch; for major updates > (2.x0) you should use a new development branch, off the trunk. > @@ -148,11 +153,6 @@ > svn commit -m "X.Y.N devel cycle started" > > (where X.Y.N is the new version number) > - > - this is the point of no-return, once this commit has been made, the > - version number is considered "burned". Even if the release is not > - made at this point, the number is locked for this particular code. > - The same number cannot be used for a future different release. > > - (for any rc, prerelease, or full release) Place the tarballs in a > private location and request a vote on [email protected] to -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFCdrCMMJF5cimLx9ARAqy0AJ9Ff/DYtdo9m0JJCHYLjNxoSjSr3ACeNfgf snNCL1Mg/odi+fm4zpEkPc4= =rW/Y -----END PGP SIGNATURE-----
