uPortal upgrade best practices

Stub

I'm hoping that someone can fill in this page with details on best practices for upgrades on minor versions of uPortal in a safe way. i.e., if I want to get from uPortal 2.3.4 to uPortal 2.4.1 (or 2.4.1 -> 2.4.2), given that there are significant code changes and several database changes, what should I do?

Technologies that can help

Version control

Using CVS to drive the upgrade process

We've put some effort into this, using CVS to drive the process. I'm in the midst of updating some notes here.
The next to last link gives some an overview of our uPortal framework process.

Cheers,
Jim

Using Subversion to drive the upgrade process

The Subversion manual outlines some very useful upgrade processes in the "General Vendor Branch Management Procedure" section:

http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

Specific upgrade paths

The code would work fine if the database were up to date.. that seems to be the place where it's tough to shoehorn changes in.

There are likely to be different upgrade paths depending for the various uPortal versions.
06 from 2.4.2 to 2.5.0