canmove, Confirmed users
637
edits
Firefox/Planning/2011-05-11: Difference between revisions
→Firefox 5 (Desktop)
| (2 intermediate revisions by 2 users not shown) | |||
| Line 36: | Line 36: | ||
* [http://blog.mozilla.com/channels/2011/05/11/merge-dates-vs-release-dates/ Blog post about when to expect the channel updates] | * [http://blog.mozilla.com/channels/2011/05/11/merge-dates-vs-release-dates/ Blog post about when to expect the channel updates] | ||
* Does that mean the Firefox 5 beta release will be before the 5.* AMO compatibility bump? | |||
** yes, quite likely. We expect to be ready to ship within a week of the merge, and since we're creating new tools for the AMO compatibility bump there's some risk to their date. After we've tested the beta merge and are ready to go we'll see where we are on the compatibility front before making the release decision. | |||
** Current 5.* add-on compatibility is 29%, half our normal compatibility when we've shipped a beta. We don't know how this will impact uptake. | |||
===Firefox 6 (Desktop) === | ===Firefox 6 (Desktop) === | ||
| Line 54: | Line 58: | ||
** Merging mozilla-central to mozilla-aurora | ** Merging mozilla-central to mozilla-aurora | ||
** Branding for Aurora has landed | ** Branding for Aurora has landed | ||
** Android package ID is org.mozilla.fennec_aurora so | ** Android package ID is org.mozilla.fennec_aurora so aurora can be installed side-by-side with other channels | ||
===Firefox Sync=== | ===Firefox Sync=== | ||
| Line 119: | Line 123: | ||
* Will there be a product-level signoff before the merge to beta, as per the [http://mozilla.github.com/process-releases/draft/development_overview/ new development process] which examines whether the [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20tracking-firefox5%3A%2B&list_id=240774 issues being tracked] are in a good enough state to merge forward to that audience? (beltzner) | * Will there be a product-level signoff before the merge to beta, as per the [http://mozilla.github.com/process-releases/draft/development_overview/ new development process] which examines whether the [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=OPEN%20tracking-firefox5%3A%2B&list_id=240774 issues being tracked] are in a good enough state to merge forward to that audience? (beltzner) | ||
** LegNeato: yes! this will happen at Monday's [Firefox/Beta|Firefox Beta] meeting | ** LegNeato: yes! this will happen at Monday's [Firefox/Beta|Firefox Beta] meeting | ||
* Axel: did mail outreach to locales on aurora yesterday, feedback says that we won't have complete status before monday. should be expecting some landings on beta post branch. open questions about double merge onto aurora as well as beta - possible impact to next merge from aurora->beta. joduinn and axel to take offline. | |||
== Actions this week == | == Actions this week == | ||
* Cheng to coordinate with product marketing and UX to determine what, if any, response we should have to the problems of 4.0 users being confused about session restore changes. | * Cheng to coordinate with product marketing and UX to determine what, if any, response we should have to the problems of 4.0 users being confused about session restore changes. | ||