Releases/Thunderbird 10.0.5esr/BuildNotes: Difference between revisions

no edit summary
No edit summary
Line 77: Line 77:
* start automation ''← monitor progress on buildbot (e.g. [http://buildbot-master34.build.mozilla.org:8001/waterfall?num_events=10&category=release-comm-esr10- comm-esr10])''
* start automation ''← monitor progress on buildbot (e.g. [http://buildbot-master34.build.mozilla.org:8001/waterfall?num_events=10&category=release-comm-esr10- comm-esr10])''
** the same command as above but without the "--dryrun"
** the same command as above but without the "--dryrun"
<font color='red'>'''DONE TO HERE'''</font>
<font color='red'>'''NOTES TRIMMED TO HERE'''</font>


=== 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,10.0.5,10.0
For 3.6.25 you would send
  Thunderbird,thunderbird,thunderbird,10.0.5esr,10.0
Firefox,firefox,firefox,3.6.25,3.6
Firefox,firefox,firefox,3.6.26pre,3.6
 
For non-3.6 releases, we need to include Fennec in the email if we build Fennec.
 
For 9.0b2 it would be
Firefox,firefox,firefox,9.0b2,9.0
Fennec,firefox-mobile,fennec,9.0b2,9.0
 
And for 9.0 final it's
Firefox,firefox,firefox,9.0,9.0
Fennec,firefox-mobile,fennec,9.0,9.0
 
ESRs look like this:
  Firefox,firefox,firefox,10.0.3,10.0
  Firefox,firefox,firefox,10.0.3esr,10.0


=== E-mail mirrors@mozilla.org ===
=== E-mail mirrors@mozilla.org ===
Not necessary for rapid release betas, files only go as far as the 'internal mirrors'.
N/A


Coordinate yourself with the person creating the ESR and the latest release which normally go out at the same time.
<font color='red'>'''DONE TO HERE'''</font>
 
<br/><font color='red'>'''NOTES TRIMMED TO HERE'''</font>
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>
Subject: Firefox {VERSION1} [and {VERSION2}] coming to mirrors on {DATE}
Body:
We're planning on pushing our Firefox {VERSION1} [and {VERSION2}] release(s) to mirrors 24 hours before {DATE}.
# If this is a chemspill, please mention that in the email as it will mean pinging
# for CDN to be enabled when the push to internal mirrors happens
 
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.
</pre>


=== Edit rsync exclude files ===
=== Edit rsync exclude files ===
Line 126: Line 95:


=== Tag ===
=== Tag ===
No problems


=== Bouncer Submitter ===
=== Bouncer Submitter ===
 
No problems


=== Source ===
=== Source ===
Confirmed users
4,293

edits