Re: PHP4/PHP5 package versions and backward compatibility

Hi Martin, On 26.01.2010 1:43, Martin Schütte wrote:

I'm somewhat confused about the rules for package naming and backward compatibility, so I would like to get advice on that. I maintain the package Payment_DTA (current version is 1.3.2 stable) and in a next version I want to drop PHP4-support (because I would like to use exceptions in new methods). The existing API will not change. Would this new version be considered as backward compatible?

Well, people running PHP4 won't be affected as they won't be able to upgrade in the first place. So the question is: would people running your package under PHP5 need to change their scripts after upgrading to a new version? If the answer is "yes" then you need to create a new package, if it is "no" you can release a new minor version.

And what will be the appropriate name/version number: - - Payment_DTA 1.4 (new minor version),

If your package remains backwards compatible.

- - Payment_DTA 2.0 (new major version), or

This is IMO not allowed with current version numbering rules.

- - Payment_DTA2 0.1 (completely new package)?

If your package isn't backwards compatible.