note
dragonchild
The very first thing you need to figure out is
<p><b>Do I need to upgrade at all?</b>
<p>Upgrading is a change. It's a massive change, actually. Is the cost of testing this change worth the benefits? What <i>are</i> the benefits? Do you have a backout plan if something breaks?
<p>Personally, I would upgrade on a case-by-case basis. If version 2.44 of the Floopy module works for you, why does it matter if the latest version is 4.55? If you never hit a bug, then you don't need the bugfixes. Plus, bugfixes might introduce bugs you're not aware of. If you need a feature in 4.55, then upgrade to it.
<p>Furthermore, the issue isn't bugs within a given module - it's bugs between modules. Integration testing is <i>expensive</i>! And, testing doesn't prove the abscence of bugs - it simply shows you haven't found any yet.
<p><i>Thinks for a second . . .</i>
<p>The biggest problem I have with your plan is that you're changing too many things at one time. Change one item, then see what happens. If nothing breaks, bake it in for a month. Then, change another thing and see what happens. Lather, rinse, repeat.
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-85580">
<p align="center"><i><font size="-2">Being right, does not endow the right to be rude; politeness costs nothing.<br>Being unknowing, is not the same as being stupid.<br>Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.<br>Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.</font></i></p>
</div></div>
442165
442165