Short release checklist

• Software tarball(s) on downloads
• Release page on downloads
• chandlerproject.org/(server)download
• Freshmeat
• Blog
• Announce@, cosmo/chandler-dev
• chandleproject.org/releasenotes
• chandlerproject.org/

Making a Cosmo Release

Detailed steps are here CosmoReleaseProcess

Making a Chandler Release

Prerequisites

Before starting a build you will need the following:

• SSH keys installed in paniolo, downloads and all 4 build platforms
• Tinderbox and Bonsai accounts and passwords
• Chandler SVN check-in priviliges

Assumptions

The instructions assume the milestone/checkpoint/release is being made from the SVN trunk. If this is not the case, you need to adjust these instructions accordingly.

Release Process

• Milestone or Release: Close the tree
  • Send an email to chandler-dev to announce tree closure and estimated time for closure
  • Set Bonsai status to closed: http://bonsai.osafoundation.org/admin.cgi
  • Set Tinderbox status to closed: http://builds.osafoundation.org/tinderbox/tbox/admintree.cgi?tree=Chandler

• Double-check the version number:
  • Version number templates
    • Checkpoint: <major><minor><milestone>.dev-r<revision #>-checkpoint<yyyymmdd>
      • Example: 0.7alpha3.dev-r11164-checkpoint20060714
    • Milestone: <major><minor><milestone>
      • Example: 0.7alpha3
    • Release: <major><minor>
      • Example: 0.7
    • Get actual milestone number from here: http://wiki.osafoundation.org/bin/view/Chandler/ChandlerMilestoneSchedule

• Using an account that has SVN checkin permission, create a tag using the version number from above as the tag name:
  • For releases, you probably want to update the bug list in the changelog in chandler/distrib/linux/changelog.
  • svn copy svn+ssh://svn.osafoundation.org/svn/chandler/trunk svn+ssh://svn.osafoundation.org/svn/chandler/tags/<tag name>
  • svn copy svn+ssh://svn.osafoundation.org/svn/localizations/chandler/trunk svn+ssh://svn.osafoundation.org/svn/localizations/chandler/tags/<tag name>
  • Check out the tag and update version.py:
    • svn co svn+ssh://svn.osafoundation.org/svn/chandler/tags/####/chandler
    • modify version.py to reflect the version info (i.e. possibly add revision/checkpoint, or remove .dev), and commit
    • modify Makefile to pick up the correct tag from the localizations svn repository
• Start on each of the full build computers the following (as user 'builder'):
  • cd ~/hardhat
  • svn up
  • rm -rf ~/singlebuild/
  • ./singlebuild.py -s -t <tag name>

• Now (on paniolo, as builder) create a new folder to check out the tagged tree, in preparation for tarring it up:
  • cd ~
  • mkdir CHAN_<tag name>
  • cd CHAN_<tag name>
  • svn export http://svn.osafoundation.org/chandler/tags/<tag name>
  • cd Chandler.<tag name>/
  • svn export http://svn.osafoundation.org/tools/hardhat hardhat
  • cd Chandler.<tag name>/external/
  • export BUILD_ROOT=`pwd`
  • make sources
  • rm -rf {db,eggtranslations,m2crypto,wx,pylint,zanshin}/*.tar.gz # Remove extraneous tarred files
  • cd ..

• Tar it up (on paniolo, as builder):
  • tar czf Chandler_src_<tag name>.tar.gz chandler hardhat external internal

• Create the snapshot directory (on paniolo, as builder):
  • cd ~/snapshots
  • Checkpoint: snapshot name is the checkpoint date as YYYMMDD mkdir <snapshot name>
  • Milestone or Release: mkdir <tag name>
  • mv ~/CHAN_<tag name>/Chandler_src_<tag name>.tar.gz <snapshot name>/
  • rm -rf ~/CHAN_<tag name> (We're done with this)

• Wait until all builds are done (around 1/2 hour). Copy build distributions to builds server. On each build machine (as builder):
  • cd ~/singlebuild/output/Chandler_<tag name>
  • scp Chan* builder@paniolo:snapshots/<snapshot name>

• Create the index pages. On paniolo (as builder):
  • cd ~
  • Checkpoint: python distIndex.py C <tag name> <snapshot name>
  • Milestone: python distIndex.py M <tag name> <snapshot name>
  • Release: python distIndex.py R <tag name> <snapshot name>

• Point your browser to http://builds.osafoundation.org and make sure that the builds show up as they should.

• If you want to make the build available via the Tools >> Check for Test Updates feature, edit http://builds.osafoundation.org/chandler/test-chandler.html to reflect the new build.

• HAVE INTERNAL FOLKS TEST IT, ESPECIALLY ON A PC W/O VISUALSTUDIO!
  • QA lab machines!
  • refer to AcceptanceTests for testing process

• Upload the milestone to the downloads server. (on paniolo, as builder):
  • ssh builder@downloads
  • cd ~/snapshots
  • mkdir <snapshot name>
  • cd <snapshot name>
  • scp -r builder@paniolo:snapshots/<snapshot name> .
  • cd ..
  • rm latest; ln -s <snapshot name> latest
  • vi index.html appropriately to indicate new release number

• Point your browser to http://downloads.osafoundation.org and make sure that the builds show up as they should.

• Open Tree
  • Open Bonsai (check timestamp, clear checkins ok, hit "open the tree" button): http://bonsai.osafoundation.org/admin.cgi
  • Open Tinderbox: http://builds.osafoundation.org/tinderbox/tbox/admintree.cgi?tree=Chandler

• If Milestone or Release then add the release info here: http://wiki.osafoundation.org/twiki/bin/view/Chandler/ChandlerReleases

• Announce it to the dev list.

Additional steps for release

• After last milestone before release, start making release candidates. Upload them to builds only. Once everyone is happy a release candidate can be made into a release, read below:

• Copy the final release candidate on builds to URL http://builds.osafoundation.org/chandler/releases/<release number>

• Edit http://builds.osafoundation.org/ so it mentions the latest build

• Copy files to downloads:/www/downloads/chandler/releases

• On downloads, in /www/downloads/chandler/releases:
  • rm latest; ln -s <release-num> latest

• Post the release announcement to the blog.

• Update http://downloads.osafoundation.org/latest-chandler.html. Note that you will frequently want to link to your blog post here, so that users can get directed there from the link on Chandler's "Update" dialog.

• Check that the page heading and links on http://chandlerproject.org/Projects/DownloadChandlerDesktop have been updated correctly by the previous step.

• Edit http://downloads.osafoundation.org/ so it mentions the latest build

• Edit http://downloads.osafoundation.org/chandler/releases/ so it mentions the latest build

• Edit http://chandlerproject.org/ to reflect the new release:
  • In the javascript, update the links in the downloadInfo dictionary
  • Also, the release number is mentioned in a _<span id="version">

• Validate your typing in the previous step :).

• Email announcement to chandler-dev@, chandler-users@, announce@. (The latter might need to be moderated).

• Update http://freshmeat.net

• Change the topic on #chandler

• Upload new plugin eggs to cheeseshop.