Next release - 0.10.0 or 1.0.0 ?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Next release - 0.10.0 or 1.0.0 ?

Andrzej Białecki-2
Hi all,

I know it's a trivial issue, but still ... When this release is out, I
propose that we should name the next release 1.0.0, and not 0.10.0. The
effect is purely psychological, but it also reflects our confidence in
the platform.

Many Open Source projects are afraid of going to 1.0.0 and seem to be
unable to ever reach this level, as if it were a magic step beyond which
they are obliged to make some implied but unjustified promises ...
Perhaps it's because in the commercial world everyone knows what a 1.0.0
release means :) The downside of the version numbering that never
reaches 1.0.0 is that casual users don't know how usable the software is
- e.g. Nutch 0.10.0 could possibly mean that there are still 90 releases
to go before it becomes usable.

Therefore I propose the following:

* shorten the release cycle, so that we can make a release at least once
every quarter. This was discussed before, and I hope we can make it
happen, especially with the help of new forces that joined the team ;)

* call the next version 1.0.0, and continue in increments of 0.1.0 for
each bi-monhtly or quarterly release,

* make critical bugfix / maintenance releases using increments of 0.0.1
- although the need for such would be greatly diminished with the
shorter release cycle.

* once we arrive at versions greater than x.5.0 we should plan for a big
release (increment of 1.0.0).

* we should use only single digits for small increments, i.e. limit them
to values between 0-9.

What do you think?


--
Best regards,
Andrzej Bialecki     <><
  ___. ___ ___ ___ _ _   __________________________________
[__ || __|__/|__||\/|  Information Retrieval, Semantic Web
___|||__||  \|  ||  |  Embedded Unix, System Integration
http://www.sigram.com  Contact: info at sigram dot com

Reply | Threaded
Open this post in threaded view
|

RE: Next release - 0.10.0 or 1.0.0 ?

sseveran
Another way of looking at it might be to ask the question what would make a great 1.0 release? What new features would be awesome? What might get people more excited?

Having a 1.0 might make the project look like it has attained a real milestone.

Steve

> -----Original Message-----
> From: Andrzej Bialecki [mailto:[hidden email]]
> Sent: Wednesday, March 28, 2007 2:38 PM
> To: [hidden email]
> Subject: Next release - 0.10.0 or 1.0.0 ?
>
> Hi all,
>
> I know it's a trivial issue, but still ... When this release is out, I
> propose that we should name the next release 1.0.0, and not 0.10.0. The
> effect is purely psychological, but it also reflects our confidence in
> the platform.
>
> Many Open Source projects are afraid of going to 1.0.0 and seem to be
> unable to ever reach this level, as if it were a magic step beyond
> which
> they are obliged to make some implied but unjustified promises ...
> Perhaps it's because in the commercial world everyone knows what a
> 1.0.0
> release means :) The downside of the version numbering that never
> reaches 1.0.0 is that casual users don't know how usable the software
> is
> - e.g. Nutch 0.10.0 could possibly mean that there are still 90
> releases
> to go before it becomes usable.
>
> Therefore I propose the following:
>
> * shorten the release cycle, so that we can make a release at least
> once
> every quarter. This was discussed before, and I hope we can make it
> happen, especially with the help of new forces that joined the team ;)
>
> * call the next version 1.0.0, and continue in increments of 0.1.0 for
> each bi-monhtly or quarterly release,
>
> * make critical bugfix / maintenance releases using increments of 0.0.1
> - although the need for such would be greatly diminished with the
> shorter release cycle.
>
> * once we arrive at versions greater than x.5.0 we should plan for a
> big
> release (increment of 1.0.0).
>
> * we should use only single digits for small increments, i.e. limit
> them
> to values between 0-9.
>
> What do you think?
>
>
> --
> Best regards,
> Andrzej Bialecki     <><
>   ___. ___ ___ ___ _ _   __________________________________
> [__ || __|__/|__||\/|  Information Retrieval, Semantic Web
> ___|||__||  \|  ||  |  Embedded Unix, System Integration
> http://www.sigram.com  Contact: info at sigram dot com

Reply | Threaded
Open this post in threaded view
|

Re: Next release - 0.10.0 or 1.0.0 ?

Dennis Kubes
In reply to this post by Andrzej Białecki-2

+1

Andrzej Bialecki wrote:
> Hi all,
>
> I know it's a trivial issue, but still ... When this release is out, I
> propose that we should name the next release 1.0.0, and not 0.10.0. The
> effect is purely psychological, but it also reflects our confidence in
> the platform.

I think that a 1.0 release signifies maturity.  And while I think there
are areas that Nutch can and will improve, I think that it has reached
the necessary maturity level.

>
> Many Open Source projects are afraid of going to 1.0.0 and seem to be
> unable to ever reach this level, as if it were a magic step beyond which
> they are obliged to make some implied but unjustified promises ...
> Perhaps it's because in the commercial world everyone knows what a 1.0.0
> release means :) The downside of the version numbering that never
> reaches 1.0.0 is that casual users don't know how usable the software is
> - e.g. Nutch 0.10.0 could possibly mean that there are still 90 releases
> to go before it becomes usable.

Personally, I don't like the x.10.x > release structure.  I guess I
think that if you can't get what you need done in 10 releases x.0.x -
x.9.x then some rework needs to be done.  Think about this, eclipse is
still only on 3.2.2 / 3.3 and they use this type of structure.

>
> Therefore I propose the following:
>
> * shorten the release cycle, so that we can make a release at least once
> every quarter. This was discussed before, and I hope we can make it
> happen, especially with the help of new forces that joined the team ;)

I agree.

>
> * call the next version 1.0.0, and continue in increments of 0.1.0 for
> each bi-monhtly or quarterly release,

I agree with bi-monthly or monthly.  I think quarterly is too long
especially considering how fast Hadoop is moving.
>
> * make critical bugfix / maintenance releases using increments of 0.0.1
> - although the need for such would be greatly diminished with the
> shorter release cycle.

Yes but some bug fixes will still be necessary even with shortened
release cycles.

>
> * once we arrive at versions greater than x.5.0 we should plan for a big
> release (increment of 1.0.0).

I am fine having 10 releases x.0 - x.9 per major release.  Maybe I don't
  understand the reason for limiting it to 5 other than.  If we do a
release every month or so then about once a year we should have a major
X release.

>
> * we should use only single digits for small increments, i.e. limit them
> to values between 0-9.

Agree.
>
> What do you think?
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Next release - 0.10.0 or 1.0.0 ?

chrismattmann
In reply to this post by Andrzej Białecki-2
My +1 for 1.0.0. I already changed it to 0.10.0, but this can be easily
reverted, and was probably something that I should have brought to the
attention of the dev list before I did that (sorry about that). In any case,
I think 1.0.0 makes a lot of sense, politically, and software wise. Nutch is
production quality software (we use it in production environments here at
JPL), and deserves to have a 1.0.0 release...

My 2 cents,
  Chris



On 3/28/07 11:38 AM, "Andrzej Bialecki" <[hidden email]> wrote:

> Hi all,
>
> I know it's a trivial issue, but still ... When this release is out, I
> propose that we should name the next release 1.0.0, and not 0.10.0. The
> effect is purely psychological, but it also reflects our confidence in
> the platform.
>
> Many Open Source projects are afraid of going to 1.0.0 and seem to be
> unable to ever reach this level, as if it were a magic step beyond which
> they are obliged to make some implied but unjustified promises ...
> Perhaps it's because in the commercial world everyone knows what a 1.0.0
> release means :) The downside of the version numbering that never
> reaches 1.0.0 is that casual users don't know how usable the software is
> - e.g. Nutch 0.10.0 could possibly mean that there are still 90 releases
> to go before it becomes usable.
>
> Therefore I propose the following:
>
> * shorten the release cycle, so that we can make a release at least once
> every quarter. This was discussed before, and I hope we can make it
> happen, especially with the help of new forces that joined the team ;)
>
> * call the next version 1.0.0, and continue in increments of 0.1.0 for
> each bi-monhtly or quarterly release,
>
> * make critical bugfix / maintenance releases using increments of 0.0.1
> - although the need for such would be greatly diminished with the
> shorter release cycle.
>
> * once we arrive at versions greater than x.5.0 we should plan for a big
> release (increment of 1.0.0).
>
> * we should use only single digits for small increments, i.e. limit them
> to values between 0-9.
>
> What do you think?
>