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

On Tue, 25 Sep 2001, Andrei Zmievski wrote: >On Tue, 25 Sep 2001, Stig Sæther Bakken wrote: >> I think we should be flexible to make this practical, the core of the >> idea is that you should not get any surprises when upgrading just "b", >> and no API surprises when upgrading "m". >> >> There's a question about whether the API should be defined as the >> source API, or also the runtime API, for extensions. I think "the >> API" should cover both. > >But then you will quickly get into double digits for the 'm' version. Like Zeev said, we release new versions too often anyway. Limit the releases with new functionality to minimum and release bug fixes more often. This way we can also reduce the amount of QA work (of bug-fix releases). And hopefully really get rid of the huge amount of bugs there still are. Also, when bug-fix releases are done, for example for 10 bug fixes, then people can update only when they know that the bug they're suffering from is really fixed. ie. the list of changes (NEWS) is not as huge as it is nowadays.. --Jani