If this is on a production server, think about other things you can do at the same time while you've got the system down. 3.1) Think about upgrading MySQL at the same time. 3.2) If yes to 3.2, you need a migration plan - especially moving up whole versions (3.xx to 4.xx, 4.xx to 5.xx). 3.3) Are there updates to apache? perl? CPAN modules? 3.4) Hardware upgrades or inspections (checked your CPU fan lately?) 3.5) OS / Kernel upgrades? I'd also flush out the session table and the who's online tables before I upgraded anything. Hope this helps! -- Cory R. King Mozi Media Group, LLC. http://www.mozimedia.com William Scott Lockwood III wrote: > Ok - with all the recient issues, I've decided I can't put off upgrading > anymore. :-( Here's my current plan of attack, with help from Colin. Anyone > see any issues, or gotchas I should look out for before I do this? > > Step 0: Back up everything! > Step 1: Copy the current Scoop directory to somewhere else > Step 2: Update the original Scoop directory to current CVS code > Step 3: Shutdown Apache > Step 4: Update the DB's with the provided script, update-db.pl > Step 5: Restart Apache > Step 6: ??? > Step 7: Profit! > > > ------------------------------------------------------------------------ > > _______________________________________________ > Scoop-help mailing list > Scoop-help at lists.kuro5hin.org > http://lists.kuro5hin.org/mailman/listinfo/scoop-help