Releases/Firefox 3.6/Post Mortem: Difference between revisions
< Releases | Firefox 3.6
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
Key question: how can we do this even better next time? | Key question: how can we do this even better next time? | ||
'''How did Firefox 3.6 measure up to the goals for the release''' | '''How did Firefox 3.6 measure up to the goals for the release?''' | ||
*faster development cycle (less than 1 yr for a meaningful product) | *faster development cycle (less than 1 yr for a meaningful product) | ||
**done...6.5 months | **done...6.5 months | ||
*deliver everything required so mobile team could ship their product the way they wanted | *deliver everything required so mobile team could ship their product the way they wanted | ||
**done | **done | ||
*improve startup time and other | *improve startup time and other perceivable ways of tracking speed | ||
**definitely faster than 3.5, but didn't really hit goal on startup time. "Perception of performance" goals were a mixed bag. | **definitely faster than 3.5, but didn't really hit goal on startup time. "Perception of performance" goals were a mixed bag. | ||
*other comments | *other comments: | ||
**define release criteria & goals more clearly up front | **define release criteria & goals more clearly up front | ||
**PR messaging around faster development cycle gets tricky - reporters start writing stories about a delayed release once it slips past initial expectations, so let's change the story to be more about why we're doing the faster releases (better for users, better for the web, etc) | |||
**nebulousness around ship date (may have) caused extra work/confusion for add-ons team...ex. Personas integration w/AMO site | |||
'''What caused delays in the delivery schedule?''' | '''What caused delays in the delivery schedule?''' | ||
Revision as of 19:17, 28 January 2010
Call in details
- Mozilla Mountain View (The Bridge)
- 650-903-0800 or 650-215-1282 x92 Conf# 8605 (US/INTL)
- 1-800-707-2533 (pin 369) Conf# 8605 (US)
- irc.mozilla.org #planning for backchannel
Agenda
Key question: how can we do this even better next time?
How did Firefox 3.6 measure up to the goals for the release?
- faster development cycle (less than 1 yr for a meaningful product)
- done...6.5 months
- deliver everything required so mobile team could ship their product the way they wanted
- done
- improve startup time and other perceivable ways of tracking speed
- definitely faster than 3.5, but didn't really hit goal on startup time. "Perception of performance" goals were a mixed bag.
- other comments:
- define release criteria & goals more clearly up front
- PR messaging around faster development cycle gets tricky - reporters start writing stories about a delayed release once it slips past initial expectations, so let's change the story to be more about why we're doing the faster releases (better for users, better for the web, etc)
- nebulousness around ship date (may have) caused extra work/confusion for add-ons team...ex. Personas integration w/AMO site
What caused delays in the delivery schedule?
What infrastructure improvements helped, and what could be improved?
Effectiveness of PR and marketing efforts, and things that could be improved
How things went on "ship day", and what could be improved