tools/release/README
author reed@reedloden.com
Tue, 29 Jan 2008 07:58:38 -0800
changeset 10915 71ec64f4a1c9eebf208e2bf5c979801c8d80a888
parent 5156 a1d9d1fd879298834b1a867280acdca7263e7848
permissions -rw-r--r--
Bug 66057 - "Proxy: $http_proxy should influence proxy settings" [p=roc@ocallahan.org (Robert O'Callahan [roc]) / diane@ghic.org (Diane Trout) / ventnor.bugzilla@yahoo.com.au (Michael Ventnor) r=josh r+sr=biesi a1.9=damons]

Bootstrap Release 
-----------------

Bootstrap is a release automation tool.
Use "release -h" for help.

Pre-flight Checklist
-----------------
There are a number of manual steps that must be performed, so a default
end-to-end run will not (yet) work.

Before any steps:

* verify shipped-locales
* edit bootstrap.cfg
* edit tinder-config.pl/mozconfig 
* version bump

After Build and Repack steps:

* rsync builds to candidates dir

After Update step:

* edit patcher config
* edit mozilla/testing/release/updates/updates.cfg

After Sign step:

* create bouncer links
* rsync builds to mirrors
* wait 12 hours for mirrors to catch up
* rsync production AUS config

Steps are in dependency order. The process may be restarted at any step as 
long as all previous steps are satisfied.

PASS/FAIL verification is run after every step.

Steps 
-----------------
1) Tag 
2) Build 
3) Source
4) Repack
5) Sign
6) Updates
7) Stage
   
Details
-----------------
Tag 
   _RELEASE and _RCn for mozilla, l10n and talkback
Build 
  en-US build from source (based on tag)
  push to stage
  announce
Source
  bz2 archive (based on tag)
  push to stage
Repack
  repack l10n, uses en-US build (based on tag)
  push to stage
  announce
Sign
  manual
Updates
  uses patcher
  generate partials and AUS config ("snippets")
  push to stage
  announce
Stage
  uses groom-files
  create release directory/filename structure
  merge updates
  announce