Re: RFC: PECL versioning
| From: | Pierre Joye | Date: | Fri, 21 Mar 2008 23:09:44 +0000 |
| Subject: | Re: RFC: PECL versioning | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-5236@lists.php.net to get a copy of this message | ||
On Fri, Mar 21, 2008 at 3:33 AM, Steph Fox <steph@zend.com> wrote:
> Hi all,
>
> There is an RFC about PECL versioning on the new izzy-whizzy Wiki.
>
> Please go and add your comments (at the end!). There needs to be consensus
> for this to work out.
>
> http://wiki.php.net/rfc
What do you mean by "Tag the version with -dev at all times except
during a package release"?
About using a recognized versionning structure, it is indeed a very
good thing and required. I would like however to go one or steps
further. Not as far as PEAR but it would be great to define some basic
rules for the x.y.z formats:
- Stable can only be >= 1.0.0
- x.y.z+1 bugs fixes, no BC allowed
- x.y+2.z features additions, bugs fixes, no BC allowed
- x+1.y.z everything is allowed
Applying these three simple rules will help distributions, packagers
and users to manage their install or to upgrade their systems in a
safe way (and faster as less tests are required).
The $Revision$ tag is pretty useless but only useful for us developers
when we work using the CVS versions or snapshots. I don't think it has
to be in the requirements.
About the replace operation in the package.xml, it is also good to do
not have it as requirements, it is only a tool that one can use or
not.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org