Hi I think a 5.0.4.1 would be the best way to go (not sure what versioning to use), as there are no real code changes to justify a 5.05. You could then provide a patch with notes for those with 5.04 installed or they could compile 5.0.4.1
I'd suggest if you rerelease the 5.0.4 as "5.0.4" then those with 5.0.4 installed will become a bit confused as to what they have installed (unless they do the checksum check). As for the CVS issue, I find in the code I write, doing a "cvs diff ." on my local directory tells me if anything is not in the repository, then I can cvs add and cvs commit once done. I then tag with the version number, roll a release package and install it on a pre production machine. Once the package is tested on a pre production machine I know that it will be ok in userspace -- if not I source the problem and roll a pre producton package again. HTH James On Apr 1, 2005 8:25 PM, Matthew Fonda <[EMAIL PROTECTED]> wrote: > > Option [a] seems like the most logical thing to do, would probably work the > best. It might be nice to note on php.net somewhere right now before this is > fixed that PEAR will not install. > > > The options we have, as far as I can tell, are: > > > > [a] Re-release 5.0.4 with that file > > [b] Release 5.0.5 with that file (seems a bit too aggressive considering > > there are no code changes, and may cause confusion) > > [c] Instruct people to install PEAR from http://go-pear.org > > > > I lean towards option [a]. Thoughts? > > > > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
