Firefox3.1/StatusMeetings/2009-01-14: Difference between revisions

 
(9 intermediate revisions by 5 users not shown)
Line 55: Line 55:
* 4 locales green, not opted in (gl (red on windows), id, ka, uk)
* 4 locales green, not opted in (gl (red on windows), id, ka, uk)
* 10 locales building and red, -2 far fetched (as, ta), -2 on the hook (ml, sl), further poke to bg, cy, da, ko, mn, oc?
* 10 locales building and red, -2 far fetched (as, ta), -2 on the hook (ml, sl), further poke to bg, cy, da, ko, mn, oc?
; string freeze break requests : gather a list of bugs for triage for breaks post Beta 3 by next week. Please CC l10n@mozilla.com and add <nowiki>[missed string freeze]</nowiki> to the whiteboard to make them show up on [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Client+Software&classification=Components&product=Core&product=Firefox&product=Toolkit&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=status_whiteboard&type0-0-0=casesubstring&value0-0-0=missed+string+freeze this query]


== QA ==
== QA ==
Line 68: Line 69:


== Release Engineering ==
== Release Engineering ==
* Formal "handover to build" date? Sunday afternoon PST is better NZ time. Do code freeze earlier on Sat maybe?
** builds needed by QA before 9am PST Tuesday 27th.
* l10n improvements, all nightlies on all branches now good.
* two unexpected downtimes since last week, all appears ok now, but let us know...


== Add-Ons ==
== Add-Ons ==
* Add-Ons are now 54% compatible with Firefox 3.1 (exactly like a week ago).
* Add-Ons are now 54% compatible with Firefox 3.1 (exactly like a week ago).
* Add-Ons review queue is beyond 600 nominated and updated Add-Ons. Details at [http://www.cesaroliveira.net/tea/archives/51 Cesar Oliveira's post].
* Add-Ons review queue is beyond 600 nominated and updated Add-Ons. Details at [http://www.cesaroliveira.net/tea/archives/51 Cesar Oliveira's post].
* Two official AMO blog posts on the topic: [http://blog.mozilla.com/addons/2009/01/09/public-service-announcement-update-your-add-ons-to-31/ from Nick] and [http://blog.mozilla.com/addons/2009/01/13/the-quick-dirty-way-to-test-your-add-ons-in-fx-31b2/ Rey]


== Partners ==
== Partners ==
Line 80: Line 86:


* On the chopping block to work with slater / bottoms on perf messaging.
* On the chopping block to work with slater / bottoms on perf messaging.
* Docs are in good shape
* Add-ons manual would be nice to have, but unlikely to happen by the end of Feb


== Marketing/PR ==
== Marketing/PR ==
Line 85: Line 93:


== Roundtable ==
== Roundtable ==
* dveditz to drive a project to see if we can have a "check your plugins" site where users can go to determine if their plugins are up to date, and if not, find links to updates (see {{bug|391433}} for details)
** beltzner, johnath, chofmann asked to be cc'd
* justin agreed to follow up with morgamic to ensure that we could throttle Major Update snippets on a per version / channel basis (to allow users to "Check for Updates..." to Firefox 3.1 on launch day, but not have the offer given to users who do not explicitly check)
* beltzner to follow up with joduinn, nthomas, axel about code handoff dates
'''Bugzilla Queries for bug verifications'''
* [http://tinyurl.com/8x9dnj 2693 bugs that were FIXED before we branched but not yet VERIFIED]
** in core, firefox or toolkit
** marked RESOLVED FIXED on trunk between 2008-07-01 and 2008-11-30 (branch date)
** not marked VERIFIED FIXED on trunk
** not marked verified1.9.1
* of the above set, [http://tinyurl.com/8eqf8y 474 were marked VERIFIED FIXED on trunk after we branched]
** in core, firefox or toolkit
** marked RESOLVED FIXED on trunk between 2008-07-01 and 2008-11-30 (branch date)
** marked VERIFIED FIXED on trunk sometime after 2008-07-01
** not marked verified1.9.1
** ([http://tinyurl.com/83ct2z 456 of these are not marked fixed1.9.1])
*** QA may wish to automatically carry the VERIFIED FIXED from trunk to verified1.9.1 for these 474 bugs, as it's the same fix that landed.
* [http://tinyurl.com/7xjo8e 438 bugs have been fixed on 1.9.1 since we branched, but not verified on branch]
** in core, firefox or toolkit
** marked fixed1.9.1 after 2008-11-30 (branch date)
** not marked verified1.9.1
** of these, [http://tinyurl.com/7xjo8e 42 have been VERIFIED FIXED on trunk]
*** Again, QA may wish to automatically carry the VERIFIED FIXED from trunk to verified1.9.1 for these 42 bugs, as it's the same code that landed.
Confirmed users, Bureaucrats and Sysops emeriti
3,599

edits