Re: [RFC] Versioning rules for PHP/Zend/PEAR/Extensions

On Mon, 24 Sep 2001, Andrei Zmievski wrote: >On Mon, 24 Sep 2001, Jani Taskinen wrote: >> 2. General rules for PHP, Zend and PEAR/C-extensions >> ---------------------------------------------------- >> >> v.m.b (e.g. 4.0.8) >> >> v = Functions removed, function behaviour changed, API changes, >> major parts rewritten. (BC might be broken) >> m = New functionality added. Only backwards compatible API changes. (100% BC) >> b = Bug fixes. No new functions added. No API changes. (100% BC) >> Left out if zero (0). > >It's going to be pretty tough to not add any functionality while also >fixing bugs. Maybe 'b' could be incremented for bug fixes and minor >functionality enhancements and 'm' for more extensive new functionality >and API changes? It's either strict or it's "forget about it". And we don't HAVE to release bug fix releases. But if we release something that provides new functionality, then then feared middle number must be bumbed up. Otherwise this all is totally useless and we can continue on this path to the unavoidable disaster. --Jani