comment on

Monks -

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?

Ideas?

In reply to Releasing a module with breaking changes by jdrago_999

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks