Re: [Numpy-discussion] Version numbers again

2006-07-27 Thread Francesc Altet
Travis, A Dijous 27 Juliol 2006 18:22, Travis Oliphant va escriure: I'm still looking for ideas on version numbering. Right now, the trunk is at version 0.9.9 but this has bug-fixes from the 1.0b1 release. The next release will be 1.0b2 and should occur in about a week. I don't really

Re: [Numpy-discussion] Version numbers again

2006-07-27 Thread Christopher Barker
Travis Oliphant wrote: When 1.0 comes out, then the trunk will be 1.0.svn_version Shouldn't the trunk then become: 1.1.0.svn_version or 1.1svn_version That would signify a development version, which I understand is what the trunk would then be. And it would be a greater version than the

Re: [Numpy-discussion] Version numbers again

2006-07-27 Thread Fernando Perez
On 7/27/06, Francesc Altet [EMAIL PROTECTED] wrote: Travis, Speaking on what we regularly do, I would choose a 1.0b2.svn_version for the trunk version. This is a way to say people: Hey, you are using a version that will be the 1.0b2 in the future.. Of course, the same meaning can be

Re: [Numpy-discussion] Version numbers again

2006-07-27 Thread Sasha
On 7/27/06, Andrew Straw [EMAIL PROTECTED] wrote: [snip] The one system that I suggest we really try to work with out-of-the-box, however, is setuptools, which, luckily, attached special meaning to .dev in a release number, so that it sorts _before_ the release. (In setuptools jargon, .dev is

Re: [Numpy-discussion] Version numbers again

2006-07-27 Thread Albert Strasheim
To: Andrew Straw Cc: Travis Oliphant; numpy-discussion Subject: Re: [Numpy-discussion] Version numbers again On 7/27/06, Andrew Straw [EMAIL PROTECTED] wrote: [snip] The one system that I suggest we really try to work with out-of-the-box, however, is setuptools, which, luckily, attached