Releases:Release Post Mortem:2014-11-25: Difference between revisions
Jump to navigation
Jump to search
m (added firefox & fennec 34.0b11) |
(added 34.0 and 31.3.0 esr) |
||
| Line 9: | Line 9: | ||
= Firefox & Fennec 34.0b11 = | = Firefox & Fennec 34.0b11 = | ||
[[Releases/Firefox_34.0b11/BuildNotes | Notes ]] | [[Releases/Firefox_34.0b11/BuildNotes | Notes ]] | ||
= Firefox & Fennec 34.0 = | |||
[[Releases/Firefox_34.0/BuildNotes | Notes ]] | |||
= Firefox 31.3.0esr = | |||
[[Releases/Firefox_31.3.0esr/BuildNotes | Notes ]] | |||
= Action items = | = Action items = | ||
Latest revision as of 18:58, 25 November 2014
Meeting Details
- 3:30pm ET
- Vidyo - Release Engineering room
- Dial-in:
- 650-903-0800 or 650-215-1282 x92 Conf# 98225 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 98225 (US)
- #releaseduty on irc.mozilla.org
- https://trello.com/b/MXHaVRcP/release-promotion-meeting
« previous week |
index |
next week »
< most recent |
upcoming >
Release Duty
- nthomas & mgerva
Firefox 34.0b10
Firefox & Fennec 34.0b11
Firefox & Fennec 34.0
Firefox 31.3.0esr
Action items
Most Wanted bugs
Roundtable
- CDN's and final verify (hwine) -- for the "we had to purge" case, it might make sense to have final verify check content on all known CDNs. It looks like that's possible doing byte range downloads, and would only extend time by about 6-9 minutes. So, "do always" or just have a builder/flag for the purge case?
- Rare procedure documentation (hwine) -- fortunately, Nick was around on his Saturday to help Liz & I with 34.0b9 fun. If what we did was "right", we should record it for posterity (especially given the new release duty rotations - some folks will get stale). Where? How?
- My first cut would be a new page with "recipes" for each situation, pointers to the existing detailed docs for specifics.