View source for Slicer3:ChangingVersionsCheckList

When preparing a new release of Slicer3:

* Create a new branch in the svn repository with the name Slicer-3-x, where x is the next even number
** See [http://www.na-mic.org/Wiki/index.php/Engineering:Subversion_Repository these svn instructions].
** Use a command line:
 svn copy http://svn.slicer.org/Slicer3/trunk/ http://svn.slicer.org/Slicer3/branches/Slicer-3-6 -m "ENH: new branch"
* Tag the svn repository for each release candidate build that will be distributed (so we can recreate the source for that binary if needed).  Use a command like:
 svn copy http://svn.slicer.org/Slicer3/branches/Slicer-3-6 http://svn.slicer.org/Slicer3/tags/Slicer-3-6-RC2 -m "ENH: tag of version of the code used to make the builds on May 15, 2010"
** don't tag it when you branch it
** tag when making release candidates
* check out the new branch using
  svn co http://svn.slicer.org/Slicer3/branches/Slicer-3-x Slicer3
* Update Slicer3/slicer_variables.tcl to reflect the svn branch 
  set ::Slicer3_TAG "http://svn.slicer.org/Slicer3/branches/Slicer-3-x"
* Update title bar via the SetName command in
  Base/GUI/vtkSlicerApplication.cxx
* Update version in binary name in getbuildtest.tcl
* Update Slicer3_VERSION_MINOR in Slicer3/CMakeLists.txt
* CPack packaging
** installer file name
** installed program name on windows
* Logos
** Welcome module
* On the svn head
** update the title bar to the next odd number, using the SetName command in Base/GUI/vtkSlicerApplication.cxx
** update CPack packaging
*** installer file name
*** installed program name on windows
** optionally update logos