Upgrade to TeamForge 6.1.1 on Red Hat

Plan your upgrade to TeamForge 6.1.1
As the first step in upgrading to TeamForge 6.1.1, consider some key questions that will affect how your new site works.

Upgrade a dedicated CollabNet TeamForge site to 6.1.1
Upgrading to TeamForge 6.1.1 on a dedicated site is easy and fun.

Upgrade an advanced TeamForge site to TeamForge 6.1.1
Upgrading to TeamForge 6.1.1 on an advanced site can be complicated but you get more flexibility and control.

Is my TeamForge site "dedicated" or "advanced?"
Check the value of the DEDICATED_INSTALL variable to see what kind of site you are working with.

Enable reporting while upgrading to TeamForge 6.1.1
When upgrading from a TeamForge 6.1 site that does not have reporting, you have to configure a collection of variables in the site-options.conf to turn on reporting in TeamForge 6.1.1.

Troubleshooting: Upgrade PostgreSQL manually
The TeamForge upgrade utility upgrades PostgreSQL for you automatically when you run the prepare-environment.sh script. However, when you upgrade to TeamForge 6.1 from TeamForge 5.4, patch 1, it is possible for the automatic PostreSQL upgrade to fail. If this happens, you can do the PostgreSQL upgrade yourself.

Install a different build of the same release
You can uninstall the current release and install a new build of the same CollabNet TeamForge release without touching your site's data.

Convert TeamForge repositories from CVS to Subversion
To convert TeamForge repositories from CVS to Subversion, use the ctf-cvs2svn.py script.