gecko-dev/tools/release
rhelmer@mozilla.com a88d6ce071 com not org
2007-08-23 01:18:23 -07:00
..
Bootstrap wait for signing log to proceed b=392969 r=cf 2007-08-22 09:09:13 -07:00
configs com not org 2007-08-23 01:18:23 -07:00
MozBuild pass build ID to FTP for use by PatcherConfig b=387970 r=preed 2007-08-14 16:53:34 -07:00
t make Config->Bump() handle no whitespace between variables b=379380 r=preed 2007-06-13 20:45:00 -07:00
bootstrap.cfg.example varibilize download/ftp/stage.m.o and replace sshUser/sshServer w/ stagingUser/stagingServer b=391968 r=cf 2007-08-20 17:32:16 -07:00
Makefile make sure to use .clean 2007-08-15 19:01:48 -07:00
README wait for signing log to proceed b=392969 r=cf 2007-08-22 09:09:13 -07:00
release wait for signing log to proceed b=392969 r=cf 2007-08-22 09:09:13 -07:00

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