|P is for Practical|
Releasing a module with breaking changesby jdrago_999 (Hermit)
|on Nov 11, 2008 at 23:52 UTC||Need Help??|
jdrago_999 has asked for the
wisdom of the Perl Monks concerning the following question:
Soon, a new release of Apache2::ASP will be made, and with it will come some breaking changes.
Changes to the $Config and $Response, mostly, but anyone upgrading from 1.x to 2.x will get bitten and will need to make some minor code adjustments.
Aside from the obvious fact that this is Generally Not Good, how should I go about letting the (albeit small) user-base of Apache2::ASP know about the upcoming changes?