Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: Planning for Backwards Compatibility

by lima1 (Curate)
on Aug 20, 2007 at 12:15 UTC ( [id://633782] : note . print w/replies, xml ) Need Help??

in reply to Planning for Backwards Compatibility

A compatibility layer (either in the same package or in a new namespace) can soon become very ugly, for example when you introduce new data structures. When such an compatibility layer would be absolutely necessary, my vote is: don't do the API changes unless the refactoring is not much more than method renamings.

Another option is a long transition phase with developer releases on CPAN. When you are happy with the new API, increment the major version number and release.

  • Comment on Re: Planning for Backwards Compatibility