Upgrading from v2.1 to v4.0

Top  Previous  Next

In October 2007, Smart Bear released version 4.0 of Code Collaborator.

This page serves to update administrators and users on considerations for upgrading.

New features

A list of major feature enhancements can be found here: http://smartbear.com/codecollab-new.php#4.0

New license codes

Version 4.0 brings a new license code system, but don't worry, it's easy.

You still have a company key, just as before, but now you will also have a license code that needs to be pasted into a field.

The trial license will usually be set up automatically, so you'll have plenty of time to notify us of your Node ID and get a new v4.0 license.

The new system does a few things for us:

Easy to reallocate a large purchase across multiple servers
Easier to issue temporary license codes for trials or new installations
No more license files to put on disk, restart the server, and all that annoying stuff
This system works the same way whether or not your server is connected to the Internet
Our back-end system lets us track your orders and upgrades more efficiently

Backward-incompatible changes to the command-line

The command-line tool is completely revamped, however almost all original commands still work exactly as before.  Here are the exceptions:

1.Use --non-interactive instead of the old, confusingly-named --quiet when you don't want the command-line prompting you for information.
2.Use --debug instead of the old, confusingly-named --verbose to create a debugging log file.
3.Use --quiet instead of --noprogress when you don't want informative output from the command-line.
4.All Perforce commands take Perforce settings (i.e. P4USER, P4CLIENT, P4PORT) first from the ccollab command-line, then from the ccollab settings (ccollab set), then from the current Perforce environment.
5.Command ccollab syncusers moved to ccollab admin syncusers.
6.Global option ccollab --help replaced with command ccollab help.
7.Global option --diffbranch moved to ccollab addchanges command option.
8.Global option --diffintegration moved to ccollab addactivity command option.
9.Command ccollab admin review-xml argument review was optional, but is now mandatory.

Server/database upgrade procedure

Upgrading the server and database to v4.0 works just like any other upgrade.  Download and execute the server installer from http://downloads.codecollab.com and follow the on-screen instructions.  All your previous settings will be preserved.

Once you upgrade to v4.0, you cannot downgrade to v2.1!  Neither the database nor the installation directory supports installing a pre-v4.0 version on top of a post-v4.0 version.

This means: Back up everything before you perform the upgrade.  This is good advice any time you upgrade any software, but it is especially important with v4.0 because you cannot "undo."

Code Reviewer v4.0 versus v3.2

For our existing Code Reviewer customers, v4.0 represents the most significant upgrade we've ever done.

A list of the new features in Code Reviewer v4.0 are here: http://smartbear.com/codecollab-codereviewer.php#cr40

Additional considerations:

Code Reviewer v4.0 and v3.2 use completely different back-ends for reviews -- the former is a database/server-based centralized system whereas the latter is a file-sharing system.
Because of the completely different back-ends, the two versions of Code Reviewer cannot see each other's reviews.
You can have v4.0 and v3.2 installed at the same time to ease the transition.