Thunderbird 2.0.0.12:BuildNotes: Difference between revisions

no edit summary
No edit summary
Line 23: Line 23:
| rowspan="2" | cvsroot/mozilla
| rowspan="2" | cvsroot/mozilla
| THUNDERBIRD_2_0_0_12_RELEASE
| THUNDERBIRD_2_0_0_12_RELEASE
|  
| GECKO181_20080128_RELBRANCH @ 2008-02-12 13:47 PST
|-
|-
| THUNDERBIRD_2_0_0_9_RC1
| THUNDERBIRD_2_0_0_9_RC1
|  
| GECKO181_20080128_RELBRANCH @ 2008-02-12 13:47 PST
|-
|-
| rowspan="2" | l10n/l10n
| rowspan="2" | l10n/l10n
| THUNDERBIRD_2_0_0_12_RELEASE
| THUNDERBIRD_2_0_0_12_RELEASE
|  
| GECKO181_20080128_RELBRANCH @ 2008-02-12 13:47 PST
|-
|-
| THUNDERBIRD_2_0_0_12_RC1  
| THUNDERBIRD_2_0_0_12_RC1  
|  
| GECKO181_20080128_RELBRANCH @ 2008-02-12 13:47 PST
|}
|}
NB: Talkback not listed, we're using pre-build binaries ({{bug|403701}}). It was still tagged because this change is very new, and the automation needs remedial lessons.


==Build data==
==Build data==
Line 72: Line 74:
|}
|}


==Notes==
==Detailed Notes==


===Automation===
===Automation===
We're using <tt>mozilla/tools/release</tt> from the <tt>RELEASE_AUTOMATION_M7_1</tt> tag, except for .../release/configs (tip).


Tagging was automated, which necessitated fudging the files that get bumped. See the bonsai link above. This step was run on build-console, as was Source.
Bootstrap tag: RELEASE_AUTOMATION_M7_1
 
Setup before starting:
 
* used existing version bump bug to attached diff for tb-moz18-bootstrap.cfg
* ensure that machines have enough resources (bug 393274)
** On production-1.8-master, remove private and public areas:
*** rm -rf /data/cltbld/firefox-*
*** rm -rf /builds/tags/* - did not do this, plenty of space
*** in /home/ftp/pub/firefox/nightly/, remove all except the 2.0.0.x-candidates directory for the previous release
*** pull in 2.0.0.9 files with <tt>rsync -av stage.mozilla.org:/home/ftp/pub/thunderbird/nightly/2.0.0.9-candidates /data/ftp/pub/thunderbird/nightly/</tt>
** On the build machines (see table aboue), checked that there was sufficient working space (~ 1GB), and stopped tinderbox. Also verified there is space available on bm-xserve04 for l10n-verify.
** On prometheus-vm, checked that there was space for another update run (4GB)
* on each machine, setup release automation using the tag above
cd /builds/release  # or /cygdrive/X/builds/release
cvs -nq up -r RELEASE_AUTOMATION_M7_1
# check for merges (M) or conflicts (C); if any found, check for local changes
cvs -q up -r RELEASE_AUTOMATION_M7_1
cd configs
cvs up -A    # in case we need to make changes later
cd ..
rm bootstrap.cfg logs
ln -s configs/tb-moz18-bootstrap.cfg bootstrap.cfg
mkdir -p old-logs/logs.tb20012/rc1
ln -s old-logs/logs.tb20012/rc1 logs
perl -c release
 
Some machines don't have the perl module Config::General so comment out
use Config::General;
at the top of <tt>Bootstrap/Step/PatcherConfig.pm</tt>. Only need this on prometheus-vm anyway, which has it.
 
====Tag====
 
On production-1.8-master in <tt>/builds/release</tt>: <tt>./release -o Tag 2>&1 | tee logs/release-Tag-RC1.log</tt>
 
===Source===
 
On production-1.8-master in <tt>/builds/release</tt>: <tt>./release -o Source 2>&1 | tee logs/release-Source-RC1.log</tt>
 
===Build===


After win32 l10n, had to set cerberus-vm back to text mode
After win32 l10n, had to set cerberus-vm back to text mode
  mount -t -sc /cygdrive
  mount -t -sc /cygdrive
so that tinderbox would run.
so that tinderbox would run.
rsync -av stage.mozilla.org:/home/ftp/pub/thunderbird/nightly/2.0.0.9-candidates /data/ftp/pub/thunderbird/nightly/
Confirmed users
4,293

edits