Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^2: Maintaining an Enterprise Perl Distribution

by seanbo (Chaplain)
on Mar 27, 2005 at 15:02 UTC ( #442625=note: print w/replies, xml ) Need Help??

in reply to Re: Maintaining an Enterprise Perl Distribution
in thread Maintaining an Enterprise Perl Distribution

I agree wholeheartly with many things you said here. Change isn't always a good thing. I strongly recommend using a test server to see what breaks when you upgrade anything before you just deploy it all over, *ESPECIALLY* if you are highly dependant on it.

In my personal experience as a system administrator, unless mandated by the need for a feature, repair of a bug or a security update, an upgrade is an unneccesary act and often times a very dangerous one. When I was new to system administration, I thought that it was important to stay "within two releases" etc as is mentioned in the initial post. I quickly realized (after a horrible problem surfaced) that my logic may have been a bit flawed. I adopted a new philosophy...upgrade when there is some need to do so, otherwise, leave it alone.

dragonchild is right about changing too many things at once as well. If something does break (and trust WILL), it will be far more difficult to find and correct the problem if you changed multiple things. If you *must* upgrade many things, do it in reasonable phases where you can simplify any troubleshooting. You will thank yourself later.

Just my $0.02.

perl -e 'print reverse qw/o b n a e s/;'
  • Comment on Re^2: Maintaining an Enterprise Perl Distribution

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://442625]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (7)
As of 2020-09-23 10:30 GMT
Find Nodes?
    Voting Booth?
    If at first I donít succeed, I Ö

    Results (131 votes). Check out past polls.