[PEPr] Comment on RFC::Drop requirement of renaming a package when migrating from PHP 4.x to PHP 5.x

+1 I think you could still maintain two branches -- if necessary. Say, the current package version (e.g. Net_SMTP) is 1.3.3. If you wanted to release a PHP5-only package, just start off with the release Net_SMTP 2.0.0-alpha (without the name change). Major version, BC break allowed. And on 1.x, you still have plenty of room to provide patches etc. for years to come. I guess in the end it's a matter of organizing releases on the pear website and the channel. It looks like that could be a reason for separate package name (e.g. Net_SMTP vs. Net_SMTP2). I haven't checked though, nor do I know the internals so this could work already. -- http://pear.php.net/pepr/pepr-proposal-show.php?id=606