y 2006 21:26
> 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 o
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,
Travis Oliphant wrote:
> 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 like having the trunk use a 'lower' ver
On 7/27/06, Francesc Altet <[EMAIL PROTECTED]> wrote:
> Travis,
> Speaking on what we regularly do, I would choose a 1.0b2. 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
> achieved i
Travis Oliphant wrote:
> When 1.0 comes out, then the trunk will be
>
> 1.0.
Shouldn't the trunk then become:
1.1.0. or 1.1
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 released
one, which is what we'd
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 rea
On 7/27/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
[snip]
> I don't really like having the trunk use a 'lower' version number than
> the releases but I'm not sure what to do. The problem seems to stem
> from wanting to have the version number sort somewhat reasonably when
> the development num
