Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
* How often do you upgrade your Perl? What version do you run in your production environments?

I move up whenever the need behooves me. Most machines I work on are still at 5.6.1. More importantly, I try to do things in a way that minimizes any breakage that might occur. This means, usually, that I try to use features available only in the lowest common denominator, which for me is 5.6.1.

* How often do you upgrade your modules? Do you try to always stay with the latest version?

I am one of those who tries to stick as close to core as possible, so when I do need a module, I install it. I usually do not have everything and the kitchen sink installed. Every once in a while, I check out the latest versions of the modules I use, and only upgrade if there is a compelling reason to do so.

* How do you deploy your Perl distributions? (install modules on each machine, autodeploy somehow, etc.)

Modules, usually. http://par.perl.org is also a good thing to look into if you are depolying apps to a customer.

* Do you include external packages (like external C libraries) in your distribution system?

http://par.perl.org will let you do this, but I again am one of those who tries to use pure Perl with as few dependencies as possible.

* Do you track what modules are actually being used? Do you remove modules that no one is using anymore (one less module to monitor and stay on top of)?

No, but I use the modules that install - i.e., I only install modules when I need them.

* How do you test your applications after a module or Perl upgrade?

I don't really - unless it *breaks*.

* We'll upgrade to the latest stable, then stay within two releases of stable.

As far as your plan goes, it is difficult to say what you should do. Do what your obligation to the customer demands. The best thing for you to do, in my opinion, is to keep current with info on the modules that you use, upgrade only if there is a compelling reason to do so, and test its effects in test environment before you blindly deploy your app that relies on untested (to you) third party software.

In reply to Re: Maintaining an Enterprise Perl Distribution by perlfan
in thread Maintaining an Enterprise Perl Distribution by cbrandtbuffalo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (4)
    As of 2019-11-20 07:37 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      Strict and warnings: which comes first?



      Results (96 votes). Check out past polls.

      Notices?