Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Release Process: Difference between revisions
Jump to navigation
Jump to search
m
we need CLIENTTAG now
m (we need CLIENTTAG now) |
|||
| Line 15: | Line 15: | ||
PULLTAG=GECKO181_20071004_RELBRANCH | PULLTAG=GECKO181_20071004_RELBRANCH | ||
#PULLTAG=MOZILLA_1_8_BRANCH | #PULLTAG=MOZILLA_1_8_BRANCH | ||
CLIENTTAG=FIREFOX_2_0_0_8_RELEASE | |||
MINIBRANCH=SEAMONKEY_1_1_5_MINIBRANCH | MINIBRANCH=SEAMONKEY_1_1_5_MINIBRANCH | ||
RELEASETAG=SEAMONKEY_1_1_5_RELEASE | RELEASETAG=SEAMONKEY_1_1_5_RELEASE | ||
| Line 25: | Line 26: | ||
echo "cvs $CVS_REPOS commit -r $MINIBRANCH -m 'initial minibranch commit' client.mk" | echo "cvs $CVS_REPOS commit -r $MINIBRANCH -m 'initial minibranch commit' client.mk" | ||
echo "mv client.mk ../client.mk.orig" | echo "mv client.mk ../client.mk.orig" | ||
echo "sed 's/$ | echo "sed 's/$CLIENTTAG/$RELEASETAG/' ../client.mk.orig > client.mk" | ||
echo "rm ../client.mk.orig" | echo "rm ../client.mk.orig" | ||
echo "cvs $CVS_REPOS commit -r $MINIBRANCH -m 'edit tags to pull from $RELEASETAG' client.mk" | echo "cvs $CVS_REPOS commit -r $MINIBRANCH -m 'edit tags to pull from $RELEASETAG' client.mk" | ||
| Line 38: | Line 39: | ||
echo "cvs $CVS_REPOS tag $RELEASETAG" | echo "cvs $CVS_REPOS tag $RELEASETAG" | ||
This outputs a list of commands to run for the tagging process, which I execute step by step, checking that the right thing is actually done. SeaMonkey usually pulls from a not-much-changing Gecko release branch near to a Firefox release tag, so we usually have a well-defined state to pull, but to make sure when pulling from that branch, I also set the CO_OPTS variable to use an exact date (automatically to the time of pulling in that script) so that the tree is 100% well-defined. | This outputs a list of commands to run for the tagging process, which I execute step by step, checking that the right thing is actually done. SeaMonkey usually pulls from a not-much-changing Gecko release branch near to a Firefox release tag (the CLIENTTAG which is set for pulling in that branch's client.mk), so we usually have a well-defined state to pull, but to make sure when pulling from that branch, I also set the CO_OPTS variable to use an exact date (automatically to the time of pulling in that script) so that the tree is 100% well-defined. | ||
The commands pull a client.mk and use it to pull a complete suite (SeaMonkey) source checkout. We're only tagging files that are part of this checkout. For versions where building own builds with the old calendar extension was still supported, we also included calendar in that pull and in our tag as well as our source tarballs (see later), but nowadays the suite pull is enough. | The commands pull a client.mk and use it to pull a complete suite (SeaMonkey) source checkout. We're only tagging files that are part of this checkout. For versions where building own builds with the old calendar extension was still supported, we also included calendar in that pull and in our tag as well as our source tarballs (see later), but nowadays the suite pull is enough. | ||