gecko/tools/release
2007-03-26 14:13:56 -07:00
..
Bootstrap use hostname in bootstrap email 2007-03-25 16:58:02 -07:00
configs Bootstrap config for Thunderbird 2 2007-03-26 14:13:56 -07:00
MozBuild Free the (distributed) Lizard! Automatic merge from CVS: Module mozilla: tag HG_REPO_INITIAL_IMPORT at 22 Mar 2007 10:30 PDT, 2007-03-22 10:30:00 -07:00
t support variable fallback b=372757 r=preed r=cf 2007-03-25 16:54:25 -07:00
bootstrap.cfg.example l10n overrides b=375006 r=preed 2007-03-25 17:18:28 -07:00
Makefile support variable fallback b=372757 r=preed r=cf 2007-03-25 16:54:25 -07:00
README Free the (distributed) Lizard! Automatic merge from CVS: Module mozilla: tag HG_REPO_INITIAL_IMPORT at 22 Mar 2007 10:30 PDT, 2007-03-22 10:30:00 -07:00
release use hostname in bootstrap email 2007-03-25 16:58:02 -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) Updates
6) Stage
7) Sign
   
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
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
Sign
  manual