Re: Re: Making a release

From: Date: Mon, 08 Mar 2004 03:42:57 +0000
Subject: Re: Re: Making a release
References: 1 2 3 4 5 6  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-863@lists.php.net to get a copy of this message
Hi Stephan, I think that the typical user should be aware of how field-tested a package is by the stability. If a package is released that has not been field-tested, there is a chance that the API will need to change when unanticipated problems are found. For most software packages, major users like ISPs wait until a version has been tested by users for months, and provide a patched version (this is what my webhost does with PHP, it always lags). PEAR's strength is that this becomes pretty much unnecessary, of course. Obviously your package is much simpler than PHP, so you have the right to do what is best for the package. I think you'll find that the alpha tag doesn't hamper the users who you'll want to do the most testing. Just check the download statistics of alpha packages that already exist. From my perspective, it's more of a protection of the meaning of stable, so if you release a beta, that's fine, it just freezes the API instantly. You'll find yourself rather quickly releasing XML_XUL2 if the API does need to be changed, and that would suck far more than calling the initial release alpha :). Here's my disclaimer: every package is unique and I'm not the author of XML_XUL, please take my suggestions as friendly suggestions, and not annoying commands, if possible :). Greg Stephan Schmidt wrote:
Hi,
Of course I could also release it as 1.0.0alpha1
Why not? When should I switch to version 1.0? The API is quite stable, there will be feature additions but I will not remove any public methods or properties. My main proble is that I'm not sure on how to determine the point I should (or am allowed) to switch to 1.0.0.... I think the whole version naming thing will complicate PEAR. If a typical user sees a package that is 0.1, he will always think that this package is immature and lacks a lot of the planned functionality. We have to make sure that people understand why the version of a package is as it is. And for this, the PEAR Group document is not sufficient. Stephan


« previous php.pear.qa (#863) next »