-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Benji York wrote: > Philipp von Weitershausen wrote: >> Stephan Richter wrote: >>> Because I disagree with that, since you cannot know the next version. >> You can always know the minimum version. If you just released 3.4.2, I >> think it's sensible to point the next release to 3.4.3. If you later >> decide that you really need a feature release, you can always bump to >> 3.5.0a1 (which would be the first release in the 3.5.x series). > > Why not leave the version totally out of the setup.py in the trunk? > After branching for a release we can set the version (e.g., 1.2), make a > release, and tag the branch. > > We could either leave the version on the branch at the "last" release or > continue the trend of mad bumping and have it at the "next" release > (which since this is a branch, we can actually predict). > > I prefer the "last" version, but "next" would work too.
I prefer neither, as I don't want to encourage people to make releases without doing the bookkeeping required to get the versions right. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+vm++gerLs4ltQ4RApbhAJ9Anxm8SDCG+b0pk6MbpPT/cqaWTgCfYebK drwMpQGfEvPMyT7x5nLAwYg= =1BCs -----END PGP SIGNATURE----- _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
