Releases/Firefox 2.0.0.13/Post-Mortem: Difference between revisions
< Releases | Firefox 2.0.0.13
Jump to navigation
Jump to search
Samuelsidler (talk | contribs) (New page: This page is for notes from the Firefox 2.0.0.12 post mortem meeting held on Thursday, March 27, 2008 at 10am PDT. == Agenda == General questions to think about: * What did we do right? W...) |
Samuelsidler (talk | contribs) (→Agenda) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
General questions to think about: | General questions to think about: | ||
* What did we do right? What worked? | * What did we do right? What worked? | ||
*# | *# Overall, a very smooth release. | ||
*# Security notices were out a week ahead of the release for the security-group and security-announce. | |||
* What did we do wrong? What didn't work? | * What did we do wrong? What didn't work? | ||
*# | *# Had website issues. It took 45 minutes for things to appear live (from stage). After that, several Europeans reported not seeing the changes on mozilla.org through the next morning. '''Sam''' will follow up with IT on why this might be. | ||
*# Pushed upyourplug changes again. '''Reed''' is removing these from trunk and pushing fixed versions to stage. We'll push them to production as well. | |||
*# IT had a "meltdown" which caused bugzilla down time. This was entirely an IT issue and they're looking to see what went wrong. This was not due to load or anything the release team could control. | |||
Latest revision as of 17:47, 27 March 2008
This page is for notes from the Firefox 2.0.0.12 post mortem meeting held on Thursday, March 27, 2008 at 10am PDT.
Agenda
General questions to think about:
- What did we do right? What worked?
- Overall, a very smooth release.
- Security notices were out a week ahead of the release for the security-group and security-announce.
- What did we do wrong? What didn't work?
- Had website issues. It took 45 minutes for things to appear live (from stage). After that, several Europeans reported not seeing the changes on mozilla.org through the next morning. Sam will follow up with IT on why this might be.
- Pushed upyourplug changes again. Reed is removing these from trunk and pushing fixed versions to stage. We'll push them to production as well.
- IT had a "meltdown" which caused bugzilla down time. This was entirely an IT issue and they're looking to see what went wrong. This was not due to load or anything the release team could control.