Calendar:HowToRelease

Release Process

Create a branch

1. Create a branch from the branch you are releasing from this creates a SUNBIRD_0_5_BRANCH from the MOZILLA_1_8_BRANCH, you also need to note the time this was done on a page like Calendar:Release:Sunbird_0.5.

cvs rtag -r MOZILLA_1_8_BRANCH -b SUNBIRD_0_5_BRANCH mozilla
Note time this is done: May 22, 21:37 CDT

2. Test that the branch was properly created by checking out from the branch.

 cvs co -r SUNBIRD_0_5_BRANCH mozilla/calendar 

Change the Version Number

• You check out the branch you just created - use standard "check out code from mozilla cvs method", just substitute in the new branch for your branch parameter
• On this branch, you change the follwing:

   *  calendar/sunbird/app/module.ver
   * calendar/sunbird/config/version.txt

• cvs -d ${CVSROOT} co -r SUNBIRD_0_5_BRANCH\

mozilla/calendar/sunbird/app/module.ver mozilla/calendar/sunbird/config/version.txt

Create a minibranch

cvs tag -b SUNBIRD_0_5_MINIBRANCH calendar/sunbird/app/module.ver \
 calendar/sunbird/config/version.txt
cvs up -r SUNBIRD_0_5_MINIBRANCH calendar/sunbird/app/module.ver \
 calendar/sunbird/config/version.txt
cvs ci -m"bumping version number on calendar/sunbird on minibranch only"

• remove firefox stuff from calendar/lightning/install.rdf

Tag the release

• run "date" before you start and use this as date stamp.

screen
cd .. (one up from mozilla)
mkdir -p tags/SUNBIRD_0_5_RC1
cd tags && ln -s SUNBIRD_0_5_RC1 SUNBIRD_0_5_RELEASE && \
  ln -s SUNBIRD_0_5_RC1 SUNBIRD_0_5_RELEASE
  

 cvs co \
 -r $BRANCH_TAG \
 -D "$PULL_DATE" \
 mozilla/client.mk
 becomes: cvs co -r SUNBIRD_0_5_BRANCH -D "2007-05-23 04:00 +0000" mozilla/client.mk