Re: [ANNOUNCEMENT] mysql-5.1 (stable) Released.

The right thing to do is to use the version number from the module structure in the extension, so that runtime checks will work. The mysql extension current has no version number (doh!) so we really should push out another release with something fixed. I guess we could break the rules just this once, and clobber the verison 5.1 package (deleting it from the site) and replacing it with 1.0. We'd need to update the main extension in HEAD to have a higher version, and then ensure that we maintain those version numbers properly. --Wez. On 9/4/05, Wez Furlong <kingwez@gmail.com> wrote: > Well, the code comes from PHP version 5.1, and by keeping the version > number consistent with the PHP from which the code was taken, we're > helping the users (and developers) know just which code is being used. > Starting at 1.0 seems "wrong" because the code has been around for > years and had numerous revisions; just because its the first package > release, doesn't mean that we have to start at 1.0. > > I'd like to push all the other core extensions up to PECL in this way; > I'm not rigid on the versioning, and I'm open to suggestions on how to > sensibly do this for those other extensions. > > --Wez. > > On 9/4/05, Lukas Smith <lsmith@php.net> wrote: > > Wez Furlong wrote: > > > Well, the number in the package.xml file was already 5.0.x, as set by hartmut. > > > We can set a policy for other extensions, but can't decrease the > > > package version for this one, since it is already released. > > > > We have a policy in PEAR that might atleast partially be sensible to be > > applied to PECL. > > > > http://pear.php.net/pepr/pepr-proposal-show.php?id=65 > > > > Hmm well I guess the key pieces it specifies is that you start below > > 1.0.0, that 1.0.0 means API stable and that you cannot go to stable > > before 1.0.0 (especially the last point is obviously controverse as alot > > of people mark things as stable but stick with a version number below > > 1.0.0 to denote that things are not yet feature complete). > > > > Beyond that it deals with BC breaking releases by forcing essentially an > > entirely new package. Its essentially what internals is currently doing > > with the idiotic "i" appending (as in mysqli, xmlrpci ..). > > > > regards, > > Lukas > > > > >