The important thing is that you're using a production release. This means that we will attempt to make sure that upgrading from 3.2.2 to 3.2.4 is easy, at least if you haven't changed anything. This means we will provide a data model upgrade script.
Your best bet is to stage your upgrade. Make a copy of your entire system (hopefully you edited a CVS-linked checkout of the code), and do a cvs update. Resolve whatever conflicts you have. Try the DB upgrade script on a "test" database that contains a clone of your production DB. Find out what conflicts you have there. In general, you're going to have a hard time if you've done significant edits to the system. That is the endless pain of customizing complex software apps: there is no easy upgrade path. Hopefully, the modularization of 4.0 and the move towards more complete templating will minimize these issues, but don't expect an upgrade of a customized system to ever be a simple command line.
