5.20 is the most recent stable release, so if they are trying to get current, that is it.
Upgrading the system perl from 5.8.8 to 5.20 however is probably not advisable though. What is the role-out & test plan? Who is responsible for fixing any code that breaks? What is the role-back plan? As fantastic as it would be, I've yet to work with anyone who actually moved forward with that on company-wide production servers after doing any real testing. You might suggest they look into perlbrew and maybe even pinto or carton as ways of managing installing 5.20 on all the production systems for deploying new code against without disrupting the system perl and everything that may depend on it. -HTH, Sean On Fri, Jun 27, 2014 at 11:17 AM, Greg London <[email protected]> wrote: > > one of the IT guys at work just asked what > I thought about installing version 5.20.0 of perl > on all our computers. > > We currently have 5.8.8. > > I don't even know if 5.20 is considered "stable" or not. > Buggy? Issues? > > Is a different version better? > > Thoughts? > > My experience with IT > (at every job I've ever worked at) > is usually one of > "You have perl 5.4, that should be good enough". > so, I wanted to make the most of this. > > Greg > > > > > > > _______________________________________________ > Boston-pm mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/boston-pm > _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
