in reply to Releasing a module with breaking changes

  1. Rename the module to something like Apache::ASP::Old or similar.
  2. Make the Apache2::ASP in CPAN, a module that when loaded warns about the future changes, telling the user to use Apache2::ASP::Old or to try the new development versions. Then load Apache::ASP::Old so nothing gets broken at this point.
  3. Release development versions using 2.xx_xx version numbers that are not automatically installed from CPAN.
  4. After a while, when the new version is stable enough, replace Apache2::ASP with the new version.

Replies are listed 'Best First'.
Re^2: Releasing a module with breaking changes
by jdrago_999 (Hermit) on Nov 13, 2008 at 19:42 UTC

    Sage advice.

    Thanks for putting these thoughts all in one spot.

    I like the Apache2::ASP::Old thing - reminds me of Class::DBI::Frozen.

[reply]

In Section Seekers of Perl Wisdom