Review the steps for Installing CiviCRM from subversion (SVN) repository to get a general idea of the procedure. This page covers the DIFFERENCES when using SVN tags.
Installing a tagged release
Check out a tagged release to start, rather than checking out from trunk or a branch:
EXAMPLE: To begin with the 3.2 Alpha 1 release:
Following the remaining steps (2 through 10) [here|CRMUPCOMING:Installing CiviCRM from subversion (SVN) repository].
You should now have a running CiviCRM site. Be sure and verify the your civicrm-version.txt file contains the version corresponding to the tag you've checked out (e.g 3.2.alpha1 Drupal PHP5 for the example we started with).
If you want to upgrade and use a copy of a production DB (i.e. from a prior version):
Updating to a new release tag
Follow these steps when you are ready to update the site to a new release tag:
Switch your local SVN repository to the new release tag:
EXAMPLE: To switch to the 3.2 Alpha 4 release:
Review the version contained in civicrm-version.txt and update to the new tag version if needed.
Update the DAO (data access object) files to the current release:
Run the CiviCRM upgrade script by logging in and navigating to:
If the upgrade script runs successfully, your site should be happily running the new release.