PHP PEAR Questions and Answers - Re: [PEAR-QA] version number for new release

Author

Re: [PEAR-QA] version number for new release

Justin Patrin

2004-07-31, 3:55 am

On Fri, 30 Jul 2004 18:17:19 +0200, Christian Wenz <chw@hauser-wenz.de> wrote:
> Hi,
>
> since the new release of HTTP_Upload is really close, one question: The
> previous release, dating back to 2002, was "0.8.1" with status "stable".
> We do not want to jump to 1.0.0 yet so we are preparing to release
> 0.9.0. However is this would violate the naming scheme. So what are the
> rules for packages that were last released using the "old" naming scheme?
>

Why aren't you ready to go to 1.0.0 yet? IMHO, 1.0.0 means stable
(that's why the naming is set up that way). It's a bit of a jump, but
it's for the sake of consistency. I agree that you should go to 1.0.0
for a new release.

--
DB_DataObject_FormBuilder - The database at your fingertips
http://pear.php.net/package/DB_DataObject_FormBuilder

paperCrane --Justin Patrin--

Arnaud Limbourg

2004-07-31, 8:55 am

> I say 0.9.0 as beta, wait a while, see if any bugs are found (give 2-4
> w

s or so), then release a RC for 1.0.0 and then 1.0.0 :)
>
> That's my opinion anyway :)

It would make sense to do that.

More than the wait it should be usage that is the indicator wether to go
stable or not. Waziting a month if nobody uses it won't showthe bugs :)))

Arnaud.

Christian Wenz

2004-07-31, 3:55 pm

Hi,

>Why aren't you ready to go to 1.0.0 yet? IMHO, 1.0.0 means stable
>(that's why the naming is set up that way). It's a bit of a jump, but
>it's for the sake of consistency. I agree that you should go to 1.0.0
>for a new release.
>
>
the thing is that we have a few points on our todo list for 1.0.0
(internal, non BC-breaking changes; one or two new features) but would
like to release an intermins release. But going straight to 1.0.0 is
also fine, then we will hold the release till everything is implemented.

Regards
Christian

Sponsored Links