To me, a lowly developer, the complaint that 'Developers B&M when I upgrade perl and it breaks their code...'
should never occur.
Change Management system are put into place just for this situation.

Mr. Sysadmin decides that there should be an upgrade from Gofer 1 to Gofer 2. He should be submitting a
Change Request to the Change Management Committee, comprised of Sys Admins, sys engineers, and developers.
His request is reviewed and Ms. Developer says, "Wait! You can't change that yet, it will break all my code!!!"
So a schedule and or a project plan is put into operation to either justify the upgrade and prepare the code for such,
or to deter the Sysadmin from performing the upgrade until the reasons for it outweigh the reasons against it.

"That that is, is... for what is that but that? and is but is?" Shakespeare, Twelfth Night, Act IV, Scene 2

"Yet THAT which is not neither is nor is not That which is!" Frater Perdurabo (pseud. Aleister Crowley), Liber CCCXXXIII, The Book of Lies

---

---

• 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.