Releases/Thunderbird 13.0.1/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 4: Line 4:
= Bugs hit =
= Bugs hit =
Enter any bugs pre-existing or newly discovered and filed during the release:
Enter any bugs pre-existing or newly discovered and filed during the release:
* {{bug|}} - description
* {{bug|763769}} - release_sanity fails due to mozconfig differences. You can skip with -m
* skipped L10n with -l since the milestone was missing (already in touch with Axel)
<pre>
2012-06-14 15:59:55,364 : ERROR : cannot find l10n dashboard at https://l10n.mozilla.org/shipping/l10n-changesets?ms=tb13.0.1
2012-06-14 15:59:55,365 : ERROR : Error verifying l10n dashboard changesets
</pre>


=Build Engineers=
=Build Engineers=
{name} - Tracking bug: {{bug|#}}
{armenzg} - Tracking bug: {{bug|763683}}


=Signed-off Revision(s)=
=Signed-off Revision(s)=
Build 1:  
Build 1:  
* comm-beta: http://hg.mozilla.org/releases/comm-beta/rev/
* comm-beta: http://hg.mozilla.org/releases/comm-beta/rev/461d927daa30
* mozilla-beta: http://hg.mozilla.org/releases/mozilla-beta/rev/
* mozilla-beta: http://hg.mozilla.org/releases/mozilla-beta/rev/f48d675ffa9f


=L10N changesets=
=L10N changesets=
* None for a .1 release
* No milestone but we're taking one change
nl b07154d0e17b


=Tags=
=Tags=
Line 26: Line 32:
|-
|-
| rowspan="2" | 1
| rowspan="2" | 1
| GECKO130_XXX_RELBRANCH THUNDERBIRD_13_0_1_BUILD1 THUNDERBIRD_13_0_1_RELEASE  
| GECKO1301_2012061416_RELBRANCH THUNDERBIRD_13_0_1_BUILD1 THUNDERBIRD_13_0_1_RELEASE  
| [http://hg.mozilla.org/releases/comm-beta/rev/ ]
| [http://hg.mozilla.org/releases/comm-release/rev/b2b140bfc565 b2b140bfc565]
|-  
|-  
| GECKO130_XXX_RELBRANCH THUNDERBIRD_13_0_1_BUILD1 THUNDERBIRD_13_0_1_RELEASE  
| GECKO1301_2012061411_RELBRANCH THUNDERBIRD_13_0_1_BUILD1 THUNDERBIRD_13_0_1_RELEASE  
| [http://hg.mozilla.org/releases/mozilla-beta/rev/ ]
| [http://hg.mozilla.org/releases/mozilla-release/rev/f48d675ffa9f f48d675ffa9f]
|}
|}


Line 66: Line 72:
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|detailed instructions]]</small>
<small>[[Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation|detailed instructions]]</small>
* Hit clobber
* Hit clobber
DONE TO HERE
<i>
* No L10n changes for a .1 release
* No L10n changes for a .1 release
* Reserve slaves:
* Reserve slaves:
Line 85: Line 89:
* update and reconfigure the master
* update and reconfigure the master
<pre>
<pre>
cd /builds/buildbot/build1/master/buildbot-configs
# make update does not work on this master due to bm34 having local changes
# make update does not work on this master due to bm34 having local changes
hg pull -u && cd ..
cd /builds/buildbot/build1
source bin/activate
cd buildbot-configs && hg pull -u && cd ..
cd buildbotcustom && hg pull -u && cd ..
cd tools && hg pull -u && cd ..
make checkconfig & make reconfig
make checkconfig & make reconfig
<pre>
cd master
cd /builds/buildbot/build1/master
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 13.0.1 --branch comm-release --build-number 1 \
source ../bin/activate
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 13.0.1 --branch mozilla-release --build-number 1 \
     --release-config release-thunderbird-comm-release.py --products thunderbird  \
     --release-config release-thunderbird-comm-release.py --products thunderbird  \
     --dryrun localhost:9001
     --dryrun localhost:9001
</pre>
</pre>
* release_sanity might fail due to mozconfig differences. You can skip with -m
* release_sanity fails due to mozconfig differences. You can skip with -m
* release_sanity fails due to missing L10n milestone. Skipped with -l


* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master13.build.mozilla.org:8001/waterfall?num_events=10&category=release-mozilla-beta- beta])''
* start automation ''&larr; monitor progress on buildbot (e.g. [http://buildbot-master34.build.mozilla.org:8001/waterfall?num_events=10&category=release-comm-release- comm-release])''
** the same command as above but without the "--dryrun"
** the same command as above but without the "--dryrun"
* reconfigure other masters (or ask the buildduty person to do this) <em>if you have done a merge (and not double-land) to production</em>


=== E-mail Metrics ===
=== E-mail Metrics ===
Use the address "metrics-alerts < AT > mozilla < PERIOD > org". <small><em>Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on <tt>#metrics</tt>.</em></small>
Use the address "metrics-alerts < AT > mozilla < PERIOD > org". <small><em>Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on <tt>#metrics</tt>.</em></small>
Thunderbird,thunderbird,thunderbird,13.0.1,13.0


=== E-mail mirrors@mozilla.org ===
=== E-mail mirrors@mozilla.org ===
They want to know approximately what time push to external mirrors will occur.  Ideally this is a 24hr notice to them, with the estimated time.
They want to know approximately what time push to external mirrors will occur.  Ideally this is a 24hr notice to them, with the estimated time.
<pre>
<pre>
Subject: Thunderbird 13.0.1 coming to mirrors on {DATE}
Subject: Thunderbird 13.0.1 coming to mirrors on tomorrow June 15th
Body:
Body:
We're planning on pushing our Thunderbird 13.0.1 release to mirrors 24 hours before {DATE}.
We're planning on pushing our Thunderbird 13.0.1 release sometime tomorrow Friday June 15th.


If you believe these releases or these dates will cause any problems,
If you believe these releases or these dates will cause any problems,
Line 116: Line 122:
status/weights/etc, please notify mirror-submissions at mozilla.org.
status/weights/etc, please notify mirror-submissions at mozilla.org.
</pre>
</pre>
=== Edit rsync exclude files ===
After getting [https://intranet.mozilla.org/Build:Setup_sysadmins_access svn setup] (auth req'd) edit files/rsync/rsyncd-mozilla-releases.exclude so that it excludes the current release, get review and deploy. This prevents external mirrors from picking up the new release prematurely.
For rapid release betas and ESR builds, this is not necessary as there's already an exclude that matches them.


=== Tag ===
=== Tag ===
 
No problems.
=== Bouncer Submitter ===
=== Bouncer Submitter ===
 
No problems.
=== Source ===
=== Source ===
 
No problems.
=== Build ===
=== Build ===
==== Thunderbird ====
==== Thunderbird ====
 
No problems.
===== Thunderbird repacks =====
===== Thunderbird repacks =====
 
No problems.
=== Checksums ===
=== Checksums ===
 
No problems.
=== Updates ===
=== Updates ===
 
No problems.
==== Update verify ====
==== Update verify ====
 
No problems.
=== Reset reserved slaves ===
=== Reset reserved slaves ===
 
Reset.
=== Check permissions / AV scan ===
=== Check permissions / AV scan ===
It is supposed to be triggered automatically after updates are done.
No problems.
File a bug if it doesn't. <small>[[Release:Release_Automation_on_Mercurial:Documentation#Antivirus_check|details]]</small>


=== Push to internal mirrors ===
=== Push to internal mirrors ===
This is done by automation for rapid release betas. '''Note''': if you have to reconfig the release buildbot master in during the release, the uptake monitoring will fail ({{bug|629648}}). That means you'll need to manually send the "ready for releasetest" emails when you believe things are "good enough". Refer to a prior release for email details.
* the rsync excludes have been updated was pushed by nthomas
 
* Forced build the push to mirrors builder
For other releases, this should be done manually at this point, after check permissions / AV scan have completed.
* Make sure the rsync excludes have been updated ([[Releases/BuildNotesTemplate#Edit_rsync_exclude_files]])
* Force build the push to mirrors builder. Make sure at least 15 minutes have elapsed since editing the rysnc module to give it time to sync out.
 
[https://intranet.mozilla.org/ReleaseEngineering/Release/Primer#Mirrors_.28internal_.26_external.29 Mirrors Policy]


=== Final verification ===
=== Final verification ===
Record receipt of "completed_final_verification" emails (1 per platform)
Record receipt of "completed_final_verification" emails (1 per platform)
 
* XXX: TODO add to bug hit section
=== Going to Beta ===
* It seems that isu.net.sa is failing
==== Run backupsnip ====
* Callek thinks that this [https://bugzilla.mozilla.org/attachment.cgi?id=633399&action=diff#files/rsync/rsyncd-mozilla-releases.exclude_sec4 patch] had not landed early enough
NOTE: Remember to do this at least '''2 hours''' ahead of the expected "go to beta" email. <small>''[[Release:Release_Automation_on_Mercurial:Documentation#Prepare_for_Beta_Release_.28Firefox_only.29|details]]''</small>
 
Remember to ssh to aus3-staging using your short LDAP name and then run <code>sudo su - ffxbld</code> once on.  If you intend to use screen, initiate your screen session while you are still yourself.


=== Before Release Day ===
=== Before Release Day ===
<!-- not for beta -->
Assuming this is not a chemspill.


==== Run backupsnip for release snippets ====
==== Run backupsnip for release snippets ====
Do this the night before release day as it can take up to two hours.
Do this the night before release day as it can take up to two hours.
 
<pre>
#tbirdbld@aus3-staging
cd /opt/aus2/snippets/staging
~/bin/backupsnip Thunderbird-13.0.1-build1
</pre>
=== Push to external mirrors ===
=== Push to external mirrors ===
If this is a chemspill you will want to ping justdave (or other sysadmin) in #release-drivers and ask them to enable CDN.
* Remove previously added blacklisting entry from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
* Remove previously added blacklisting entry from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
* Replace old version with the current one in stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude
* Replace old version with the current one in stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude
* Pushed to SVN to update stage.mozilla.org


See [https://intranet.mozilla.org/RelEngWiki/index.php/Managing_Rsync_Modules details]
==== Push to Release Channel ====
 
=== Release Day ===
==== Check Throttling  ====
* XXX: Does this apply to Thunderbird?
 
See http://update-watch.localgho.st/release/ for example AUS links
 
Some links to check:
* Automatic (idle time check) update links:
** 10.0.2 en-US [https://aus3.mozilla.org/update/1/Firefox/10.0.2/20120215223356/WINNT_x86-msvc/en-US/release/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86-gcc3/en-US/release/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86_64-gcc3/en-US/release/update.xml linux64]
** 9.0 en-US [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/WINNT_x86-msvc/en-US/release/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86-gcc3/en-US/release/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86_64-gcc3/en-US/release/update.xml linux64]
** 10.0.2esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/WINNT_x86-msvc/en-US/esr/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86-gcc3/en-US/esr/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86_64-gcc3/en-US/esr/update.xml linux64]
** 10.0esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/WINNT_x86-msvc/en-US/esr/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86-gcc3/en-US/esr/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml mac] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86_64-gcc3/en-US/esr/update.xml linux64]
** 3.6.27 en-US [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/WINNT_x86-msvc/en-US/release/update.xml win32] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Linux_x86-gcc3/en-US/release/update.xml linux] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Darwin_x86-gcc3-u-ppc-i386/en-US/release/update.xml mac]
* Manual update links:
** 10.0.2 en-US [https://aus3.mozilla.org/update/1/Firefox/10.0.2/20120215223356/WINNT_x86-msvc/en-US/release/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86-gcc3/en-US/release/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120215223356/Linux_x86_64-gcc3/en-US/release/update.xml?force=1 linux64]
** 9.0 en-US [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/WINNT_x86-msvc/en-US/release/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86-gcc3/en-US/release/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/release/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/9.0/20111216140209/Linux_x86_64-gcc3/en-US/release/update.xml?force=1 linux64]
** 10.0.2esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/WINNT_x86-msvc/en-US/esr/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86-gcc3/en-US/esr/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/10.0.2/20120216092139/Linux_x86_64-gcc3/en-US/esr/update.xml?force=1 linux64]
** 10.0esr en-US [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/WINNT_x86-msvc/en-US/esr/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86-gcc3/en-US/esr/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/esr/update.xml?force=1 mac] [https://aus2.mozilla.org/update/1/Firefox/10.0/20120130064731/Linux_x86_64-gcc3/en-US/esr/update.xml?force=1 linux64]
** 3.6.27 en-US [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/WINNT_x86-msvc/en-US/release/update.xml?force=1 win32] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Linux_x86-gcc3/en-US/release/update.xml?force=1 linux] [https://aus2.mozilla.org/update/1/Firefox/3.6.27/20120216013254/Darwin_x86-gcc3-u-ppc-i386/en-US/release/update.xml?force=1 mac]
 
==== Push to Release Channel (for beta releases and release releases) ====
Once there is enough uptake and we get "go" from release driver.
Once there is enough uptake and we get "go" from release driver.
</i>
#tbirdbld@aus3-staging
cd /opt/aus2/snippets/staging
~/bin/pushsnip Thunderbird-13.0.1-build1

Latest revision as of 19:02, 15 June 2012

Notes About Releasing

Please update the Notes Template and the Release:Primer for future releases (bug fixes, changes to automation) as needed

Bugs hit

Enter any bugs pre-existing or newly discovered and filed during the release:

  • bug 763769 - release_sanity fails due to mozconfig differences. You can skip with -m
  • skipped L10n with -l since the milestone was missing (already in touch with Axel)
2012-06-14 15:59:55,364 : ERROR : cannot find l10n dashboard at https://l10n.mozilla.org/shipping/l10n-changesets?ms=tb13.0.1
2012-06-14 15:59:55,365 : ERROR : Error verifying l10n dashboard changesets

Build Engineers

{armenzg} - Tracking bug: bug 763683

Signed-off Revision(s)

Build 1:

L10N changesets

  • No milestone but we're taking one change
nl b07154d0e17b

Tags

Manually tag the automation code, then record the generated tags below. (details)

Build # Branch, Tags Changeset
1 GECKO1301_2012061416_RELBRANCH THUNDERBIRD_13_0_1_BUILD1 THUNDERBIRD_13_0_1_RELEASE b2b140bfc565
GECKO1301_2012061411_RELBRANCH THUNDERBIRD_13_0_1_BUILD1 THUNDERBIRD_13_0_1_RELEASE f48d675ffa9f

Build data

Thunderbird

Build # Type Build ID Build machine Time to build
1 Linux
Linux64
Mac
Windows

Notes

Build 1

Preparing to start Automation

detailed instructions

  • Hit clobber
  • No L10n changes for a .1 release
  • Reserve slaves:
[cltbld@buildbot-master34 master]$ pwd
/builds/buildbot/build1/master
[cltbld@buildbot-master34 master]$ cat reserved_slaves
8
  • create a symlink (since bug 725839 is not resolved)
# tbirdbld@stage
cd /pub/mozilla.org/thunderbird/nightly/
mkdir ../candidates/13.0.1-candidates
ln -s ../candidates/13.0.1-candidates 13.0.1-candidates
  • Land automation configs
  • Tagged buildbot-configs, buildbotcustom, & tools with build & release tags.
  • update and reconfigure the master
# make update does not work on this master due to bm34 having local changes
cd /builds/buildbot/build1
source bin/activate
cd buildbot-configs && hg pull -u && cd ..
cd buildbotcustom && hg pull -u && cd ..
cd tools && hg pull -u && cd ..
make checkconfig & make reconfig
cd master
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u armenzg -V 13.0.1 --branch comm-release --build-number 1 \
    --release-config release-thunderbird-comm-release.py --products thunderbird  \
    --dryrun localhost:9001
  • release_sanity fails due to mozconfig differences. You can skip with -m
  • release_sanity fails due to missing L10n milestone. Skipped with -l
  • start automation ← monitor progress on buildbot (e.g. comm-release)
    • the same command as above but without the "--dryrun"

E-mail Metrics

Use the address "metrics-alerts < AT > mozilla < PERIOD > org". Note for first-time-releasers: your email will get held for moderator approval - that is expected. If it happens more than once, get help on #metrics.

Thunderbird,thunderbird,thunderbird,13.0.1,13.0

E-mail mirrors@mozilla.org

They want to know approximately what time push to external mirrors will occur. Ideally this is a 24hr notice to them, with the estimated time.

Subject: Thunderbird 13.0.1 coming to mirrors on tomorrow June 15th
Body:
We're planning on pushing our Thunderbird 13.0.1 release sometime tomorrow Friday June 15th.

If you believe these releases or these dates will cause any problems,
please notify release at mozilla.com. If you have any problems with mirror
status/weights/etc, please notify mirror-submissions at mozilla.org.

Tag

No problems.

Bouncer Submitter

No problems.

Source

No problems.

Build

Thunderbird

No problems.

Thunderbird repacks

No problems.

Checksums

No problems.

Updates

No problems.

Update verify

No problems.

Reset reserved slaves

Reset.

Check permissions / AV scan

No problems.

Push to internal mirrors

  • the rsync excludes have been updated was pushed by nthomas
  • Forced build the push to mirrors builder

Final verification

Record receipt of "completed_final_verification" emails (1 per platform)

  • XXX: TODO add to bug hit section
  • It seems that isu.net.sa is failing
  • Callek thinks that this patch had not landed early enough

Before Release Day

Run backupsnip for release snippets

Do this the night before release day as it can take up to two hours.

 #tbirdbld@aus3-staging
 cd /opt/aus2/snippets/staging
 ~/bin/backupsnip Thunderbird-13.0.1-build1

Push to external mirrors

  • Remove previously added blacklisting entry from stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-releases.exclude
  • Replace old version with the current one in stage.mozilla.org:/pub/mozilla.org/zz/rsyncd-mozilla-current.exclude
  • Pushed to SVN to update stage.mozilla.org

Push to Release Channel

Once there is enough uptake and we get "go" from release driver.

#tbirdbld@aus3-staging
cd /opt/aus2/snippets/staging
~/bin/pushsnip Thunderbird-13.0.1-build1