Releases/Firefox 3.0.6/Post Mortem: Difference between revisions
< Releases | Firefox 3.0.6
Jump to navigation
Jump to search
Samuelsidler (talk | contribs) (New page: The following are the meeting notes from the Firefox 3.0.6 post-mortem held on Friday, February 6, 2009 at 12:00pm PST. == Development == # [issue here] == QA == # [issue here] == Build...) |
(→IT) |
||
| Line 11: | Line 11: | ||
== IT == | == IT == | ||
# One of bouncer's db servers wasn't running, which caused updates to fail ({{bug|476753}}. Had to pull/push updates a few times while trying to get it working. Why was the server not up and running? How do we ensure this doesn't happen in the future? | # One of bouncer's db servers wasn't running, which caused updates to fail ({{bug|476753}}). Had to pull/push updates a few times while trying to get it working. Why was the server not up and running? How do we ensure this doesn't happen in the future? | ||
# Had to throttle bits after release ({{bug|476875}} because mirrors couldn't handle load. Why? How do we ensure this doesn't happen in the future? | # Had to throttle bits after release ({{bug|476875}}) because mirrors couldn't handle load. Why? How do we ensure this doesn't happen in the future? | ||
== Websites == | == Websites == | ||
# [issue here] | # [issue here] | ||
Revision as of 17:30, 5 February 2009
The following are the meeting notes from the Firefox 3.0.6 post-mortem held on Friday, February 6, 2009 at 12:00pm PST.
Development
- [issue here]
QA
- [issue here]
Build
- [issue here]
IT
- One of bouncer's db servers wasn't running, which caused updates to fail (bug 476753). Had to pull/push updates a few times while trying to get it working. Why was the server not up and running? How do we ensure this doesn't happen in the future?
- Had to throttle bits after release (bug 476875) because mirrors couldn't handle load. Why? How do we ensure this doesn't happen in the future?
Websites
- [issue here]