Re: Re: [ANNOUNCEMENT] OLE-0.5 (beta) Released.

I have an idea: Why not add RC as a status? Beta can remain beta and malleable API, and RC is frozen. This more closely fits the PHP core versioning as well. Greg Pierre-Alain Joye wrote:

On Mon, 15 Dec 2003 09:43:47 +0100 "Lukas Smith" <smith@backendmedia.com> wrote:

Basically at the point where you move to beta you should be very confident about your API. However I don't see a reason why you may not have a BC break during the beta cycle for a new major version.

The beta status fits well for RC. If you are still not sure about APIs specs you should stay in alpha state. We can expect usages of beta releases in preproduction environment. As I already do, to be ready once the stable release is fired (or a few days/weeks after). And especially to do not reinvent the wheel if a specific feature is already present in an upcoming release.

This would be counterproductive. People shouldn't rely on beta APIs.

Testing your current codes with upcoming releases is not counterproductive. That's why beta exists. I'm not sure but it seems you are confused between version nuùber, release status and lacks of releases management in some cases by some developers. pierre