Firefox/Beta/2011-06-27: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
* Current plan is to do the migrations and updates on the same day | * Current plan is to do the migrations and updates on the same day | ||
* Do we want to adjust this before trying it? | * Do we want to adjust this before trying it? | ||
** Source migration, update generation, and offering the updates are 3 distinct operations | |||
** For release, everything is done beforehand except offering updates | |||
** Marketing may like everything released on the same date to grow the Beta and Aurora audiences | |||
** Migrating on the day we said is important | |||
** Waiting a couple of days to offer Aurora nightlies anyway due to increased churn | |||
** Need to manually build mozilla-beta after the source migration, which means it won't be offering it on Tuesday ever | |||
** '''All this means that even though we do a couple things on the same day, the mechanics spread out the work and the update offers over multiple days''' | |||
* Aurora vs Beta update rate? | * Aurora vs Beta update rate? | ||
** Decided this was better handled in the Aurora meeting | |||
== Firefox 5 tracking bugs == | == Firefox 5 tracking bugs == | ||
Revision as of 18:36, 28 June 2011
Early mozilla-aurora uplift?
- Carry-over from previous aurora meetings
- RelEng says they can do it but as far as resources are concerned but would prefer not
- QA says they want a couple of days to qualify as well
- We'd have to source migrate twice, worth it?
- Benefits to being consistent
- Decided to just wait until July 5th
Same day migration and channel updates?
- Current plan is to do the migrations and updates on the same day
- Do we want to adjust this before trying it?
- Source migration, update generation, and offering the updates are 3 distinct operations
- For release, everything is done beforehand except offering updates
- Marketing may like everything released on the same date to grow the Beta and Aurora audiences
- Migrating on the day we said is important
- Waiting a couple of days to offer Aurora nightlies anyway due to increased churn
- Need to manually build mozilla-beta after the source migration, which means it won't be offering it on Tuesday ever
- All this means that even though we do a couple things on the same day, the mechanics spread out the work and the update offers over multiple days
- Aurora vs Beta update rate?
- Decided this was better handled in the Aurora meeting
Firefox 5 tracking bugs
- Anything we still need to track?
- Do we clear out the list?
Action Item
- Christian will make a channel blog post about the source code migration / update details