On 12:25 pm, [email protected] wrote:
On Thu, Oct 8, 2009 at 6:40 PM, Zooko Wilcox-O'Hearn <[email protected]>
wrote:
What we do in the Tahoe-LAFS project is we don't count down to a
future
version, we only count up from a past version. �This is also what
Twisted
does (no coincidence -- we probably got the idea from them).
To clarify: that means that a beta for 2.0.0 might have a version of
1.6.3-r4321?
I'm not sure how zooko does this for Tahoe, but with Twisted (with which
we don't do "betas" but we do do "pre-releases") if we were to start
getting ready for 2.0.0, then we would create a release branch and
change the version in that release branch to 2.0.0pre1. This, of
course, complicates the matter. :) I don't think anyone has considered
how our pre-release version numbers sort compared to the rest of our
version numbers. After 2.0.0 final is released, we merge the release
branch back into trunk, changing the trunk version to 2.0.0-r54321.
Jean-Paul
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
