Confirmed users
3,816
edits
Calendar:HowToRelease: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Release Process = | = Release Process = | ||
NOTES: | |||
* ${BRANCH_TAG} is the header for the BRANCH - for sunbird 0.5 this was SUNBIRD_0_5, other releases should follow the same convention | |||
== Create a branch == | == Create a branch == | ||
1. Create a branch from the branch you are releasing from this creates a | 1. Create a branch from the branch you are releasing from this creates a ${BRANCH_TAG}_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]]. | ||
<pre> | <pre> | ||
cvs rtag -r MOZILLA_1_8_BRANCH -b | cvs rtag -r MOZILLA_1_8_BRANCH -b ${BRANCH_TAG}_BRANCH mozilla | ||
Note time this is done: May 22, 21:37 CDT</pre> | Note time this is done: May 22, 21:37 CDT</pre> | ||
2. Test that the branch was properly created by checking out from the branch. | 2. Test that the branch was properly created by checking out from the branch. | ||
<pre> cvs co -r | <pre> cvs co -r ${BRANCH_TAG}_BRANCH mozilla/calendar </pre> | ||
== Change the Version Number == | == 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 | * 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: | * On this branch, you change the follwing: | ||
* | * calendar/sunbird/app/module.ver | ||
* calendar/sunbird/config/version.txt | * calendar/sunbird/config/version.txt | ||
* cvs -d ${CVSROOT} co -r | * Then you: | ||
<pre>cvs -d ${CVSROOT} co -r ${BRANCH_TAG}_BRANCH\ | |||
mozilla/calendar/sunbird/app/module.ver mozilla/calendar/sunbird/config/version.txt | mozilla/calendar/sunbird/app/module.ver mozilla/calendar/sunbird/config/version.txt | ||
</pre> | |||
==Create a minibranch== | ==Create a minibranch== | ||
<pre> | <pre> | ||
cvs tag -b | cvs tag -b ${BRANCH_TAG}_MINIBRANCH calendar/sunbird/app/module.ver \ | ||
calendar/sunbird/config/version.txt | calendar/sunbird/config/version.txt | ||
cvs up -r | cvs up -r ${BRANCH_TAG}_MINIBRANCH calendar/sunbird/app/module.ver \ | ||
calendar/sunbird/config/version.txt | calendar/sunbird/config/version.txt | ||
cvs ci -m"bumping version number on calendar/sunbird on minibranch only" | cvs ci -m"bumping version number on calendar/sunbird on minibranch only" | ||
| Line 29: | Line 35: | ||
== Tag the release == | == Tag the release == | ||
* run "date" before you start and use this as date stamp. | * run "date" before you start and use this as date stamp. | ||
* the date should be in UTC and have this format: "yyyy-mm-dd hh:mm +0000" | |||
* You need to use an RC here in case we have RC builds that way RCs will move forward to the release (you can have multiple RC's but there is only one release) so ${RC} becomes 1 for the first attempt to release 0.5 | |||
<pre> | <pre> | ||
screen | screen | ||
cd .. (one up from mozilla) | cd .. (one up from mozilla) | ||
mkdir -p tags/ | mkdir -p tags/${BRANCH_TAG}_RC${RC} | ||
cd tags && ln -s | cd tags && ln -s ${BRANCH_TAG}_RC${RC} ${BRANCH_TAG}_RELEASE && \ | ||
ln -s | ln -s ${BRANCH_TAG}_RC${RC} ${BRANCH_TAG}_RELEASE | ||
</pre> | |||
Next, check out mozilla/client.mk and any <something>/config/mozconfig files you need with statements like this: | |||
<pre> | |||
cvs co \ | cvs co \ | ||
-r $BRANCH_TAG \ | -r $BRANCH_TAG \ | ||
-D "$PULL_DATE" \ | -D "$PULL_DATE" \ | ||
mozilla/client.mk | mozilla/client.mk | ||
becomes: cvs co -r | becomes: cvs co -r ${BRANCH_TAG}_BRANCH -D "2007-05-23 04:00 +0000" mozilla/client.mk | ||
</pre> | |||