preed%mozilla.com c57054c6d2 Bug 364088: A couple of fixes to the Stage step, including:
- use strict
-- find() needs a function ref, not a function;
-- Move the getgrnam() for the product down to where it's used
-- ja.xpi was not removed for mac (which is ja-JP-mac.xpi)
-- the ja-JP-mac.xpi regex for win32 and linux weren't quite right
-- there was a comment referencing deletion of zip files, but no code to do it
r=rhelmer


git-svn-id: svn://10.0.0.236/trunk@217830 18797224-902f-48f8-a5cc-f745e15eee43
2007-01-05 19:53:08 +00:00
..
2006-12-05 19:13:34 +00:00
2006-12-05 19:58:38 +00: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