-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reinout van Rees wrote:
On 2009-10-08, Ian Bicking i...@colorstudy.com wrote:
So after creating, say, version 0.3.1, I always mark a package as 0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might be the next
At 01:45 PM 10/13/2009 -0400, Tres Seaver wrote:
Reinout van Rees wrote:
On 2009-10-08, Ian Bicking i...@colorstudy.com wrote:
So after creating, say, version 0.3.1, I always mark a package
as 0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might be the
Reinout van Rees wrote:
On 2009-10-08, Ian Bicking i...@colorstudy.com wrote:
So after creating, say, version 0.3.1, I always mark a package as 0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might be the next level). So, it would be better to use something
On Thu, Oct 8, 2009 at 6:40 PM, Zooko Wilcox-O'Hearn zo...@zooko.com 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
Ian Bicking i...@colorstudy.com writes:
So after creating, say, version 0.3.1, I always mark a package as
0.3.2dev.
Why not just mark it 0.3.2 during development, and change the version
string in a later revision if warranted?
But this is annoying, you might never create a version 0.3.2
On 12:25 pm, be...@zope.com wrote:
On Thu, Oct 8, 2009 at 6:40 PM, Zooko Wilcox-O'Hearn zo...@zooko.com
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
exar...@twistedmatrix.com wrote:
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.
Chris Withers wrote:
I'm +1 on the branch having a version of 1.6.3~dev after 1.6.3 has
been released, and I like 2.0.0pre1 too :-)
I'm -1 on ~ meaning afterwards, because in Debian package versions it
means the exact opposite.
-Andrew
___
Andrew Straw wrote:
Chris Withers wrote:
I'm +1 on the branch having a version of 1.6.3~dev after 1.6.3 has
been released, and I like 2.0.0pre1 too :-)
I'm -1 on ~ meaning afterwards, because in Debian package versions it
means the exact opposite.
I'm neutral on the exact spelling, I just
On Friday,2009-10-09, at 6:25 , Benji York wrote:
On Thu, Oct 8, 2009 at 6:40 PM, Zooko Wilcox-O'Hearn
zo...@zooko.com 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
On Fri, Oct 09, 2009 at 01:24:50PM -, exar...@twistedmatrix.com wrote:
On 12:25 pm, be...@zope.com wrote:
On Thu, Oct 8, 2009 at 6:40 PM, Zooko Wilcox-O'Hearn
zo...@zooko.com 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
So after creating, say, version 0.3.1, I always mark a package as 0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might be the next level).
So, it would be better to use something like 0.3.1~dev. What is considered
best practice for this? Ideally something that
On Thu, Oct 8, 2009 at 5:41 PM, Ian Bicking i...@colorstudy.com wrote:
So after creating, say, version 0.3.1, I always mark a package as 0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might be the next level).
So, it would be better to use something like
On Thu, Oct 8, 2009 at 5:06 PM, Jim Fulton j...@zope.com wrote:
On Thu, Oct 8, 2009 at 5:41 PM, Ian Bicking i...@colorstudy.com wrote:
So after creating, say, version 0.3.1, I always mark a package as
0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might
On Thursday,2009-10-08, at 15:41 , Ian Bicking wrote:
So after creating, say, version 0.3.1, I always mark a package as
0.3.2dev. But this is annoying, you might never create a version
0.3.2 (e.g., 0.4 might be the next level).
So, it would be better to use something like 0.3.1~dev. What
On Thu, Oct 08, 2009 at 04:41:25PM -0500, Ian Bicking wrote:
So after creating, say, version 0.3.1, I always mark a package as 0.3.2dev.
But this is annoying, you might never create a version 0.3.2 (e.g., 0.4
might be the next level).
So, it would be better to use something like 0.3.1~dev.
2009/10/9 Jim Fulton j...@zope.com:
I like using a version of 0 on my project trunks. I set the release
version on release tags.
I really wish there was a special version (or a version pattern) that
indicated that something is a development version *only* and can't be
released. I don't
17 matches
Mail list logo
