pjs/tools/release
nrthomas@gmail.com 0c161db50c Bug 428063, need to support long names with RC for the previous version too (update verify fix for 3.0rc1 -> 3.0rc2), r=bhearsum 2008-05-08 09:45:18 -07:00
..
Bootstrap Bug 428063, need to support long names with RC for the previous version too (update verify fix for 3.0rc1 -> 3.0rc2), r=bhearsum 2008-05-08 09:45:18 -07:00
MozBuild search for buildid as printed by post-mozilla-rel.pl::main() not the update-specific code b=415180 r=nthomas 2008-03-12 16:03:55 -07:00
bin bug 428063: support major releases & quit using rc in overloaded ways. r=rhelmer,bhearsum, patch=nrthomas 2008-04-28 06:48:21 -07:00
configs For Bug 428063, need oldAppVersion for update verify when testing 3.0rc1 --> 3.0rc2 2008-05-08 07:12:15 -07:00
t do not overwrite tinder-config.pl in-place like that 2007-10-01 16:41:04 -07:00
Makefile bug 428063: support major releases & quit using rc in overloaded ways. r=rhelmer,bhearsum, patch=nrthomas 2008-04-28 06:48:21 -07:00
README wait for signing log to proceed b=392969 r=cf 2007-08-22 09:09:13 -07:00
bootstrap.cfg.example merge staging to production b=427166 r=nthomas 2008-04-08 09:40:11 -07:00
release wait for signing log to proceed b=392969 r=cf 2007-08-22 09:09:13 -07:00

README

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