Confirmed users
2,492
edits
Firefox/Aurora/2011-04-28: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
==Agenda== | ==Agenda== | ||
Topics to cover in today's meeting. | |||
* Aurora meeting schedule. | * Aurora meeting schedule. | ||
* Plan for security bug triage and nominations. | * Plan for security bug triage and nominations. | ||
* Plan for increasing user base on Beta and Aurora channels. | * Plan for increasing user base on Beta and Aurora channels. | ||
* Status of Beta build | * Beta plan | ||
* | ** Status of the Beta build | ||
** Dependencies | |||
** Increasing user base on channel | |||
** Timeline | |||
* Communications. | * Communications. | ||
* Bug triage. | * Bug triage. | ||
| Line 12: | Line 17: | ||
===Aurora meeting schedule=== | ===Aurora meeting schedule=== | ||
* | * A decision was made to keep the current meeting time for now - 2:00pm PDT on Tues and Thurs. | ||
* We understand that many will not be able to accommodate this time - still concerns here. We are not the only team finding it difficult to schedule in that key time frame of 10:00am-12:00pm PST. | |||
* This might be an issue to discuss at a forum in the future. | |||
===Plan for security bug triage and nominations=== | ===Plan for security bug triage and nominations=== | ||
* The security team will be responsible for triaging all tracking? and tracking+ *security* bugs and monitoring their progress | * Proposal: The security team will be responsible for triaging all tracking? and tracking+ *security* bugs and monitoring their progress. | ||
* In some cases the security team may go ahead and simply set tracking+ | ** In some cases the security team may go ahead and simply set tracking+ for *security* bugs bypassing the nomination. | ||
* This triage along with monitoring the progress will happen during the weekly critsmash | ** This triage along with monitoring the progress will happen during the weekly critsmash meetings. | ||
* This largely means that the Aurora triage team will skip over these *tracking* bugs during their triage sessions. They still may ping the security team about a particular bug if they see something that hasn't made progress. | ** This largely means that the Aurora triage team will skip over these *tracking* bugs during their triage sessions. They still may ping the security team about a particular bug if they see something that hasn't made progress. | ||
* The Aurora triage team will be responsible for approving the patches for the security bugs as part of their regular triage process. | ** The Aurora triage team will be responsible for approving the patches for the security bugs as part of their regular triage process. | ||
* Everyone is in favor of moving forward with this plan. | |||
===Beta plan=== | |||
====Status=== | |||
* The work for getting the beta ready is tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=652641 bug 652641]. | |||
* QA currently has the signed builds. | |||
* The earliest the Beta will be ready to push out is on Monday May 2nd (we are still blocked on some dependencies). | |||
* We will discuss this in Monday's Beta channel meeting. | |||
===Dependencies=== | |||
* A few things need to happen before we can push this out. | |||
** QA will have to test the channel changer. | |||
** QA is blocked on testing the channel changer until an AUS piece has been completed - tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=653312 Bug 653312]. | |||
** We need to have the the snippets ready for moving some beta users over - Tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=651982 bug 651982] (See next section for details) | |||
===Plan for increasing user base on Beta and Aurora channels=== | ====Plan for increasing user base on Beta and Aurora channels==== | ||
* Tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=651982 bug 651982] | * Tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=651982 bug 651982] | ||
* | * We are currently generating the MU snippets - comment #3. | ||
* Plan is to offer snippets | * Plan is to offer snippets to users until we reach 100K users. This DOES NOT include anybody on 4.0.1 and 4.0rc. The list of versions is in bug 651982. | ||
* Laura: 2 blog posts on dev planning. | * Laura: This will be coordinated with 2 blog posts on dev planning. | ||
* | ** One is for Aurora users and asking them to try the channel changer - about:home google page snippet. | ||
** Second is for beta users explaining what the channel changer - using a first run page linked to the blog post. | |||
* Anyone on any of these versions will be offered a prompted update until we get 100K then we will turn it off. Anyone that didn't get the prompt can manually go and get the update. | |||
====Next Actions=== | |||
* Meet on Monday May 2nd during Beta meeting to finalize timeline. | |||
* John owns the task to go to IT and turn on the snippets when we are ready. | |||
* John will send an email to real drivers since Christian is away. | |||
===Communications=== | |||
* PR and creative would normally get communications about this stuff on release drivers ie: what is happening when. | |||
* Some people feel like they aren't getting the information. | |||
* We could also use the all-hands on Monday - Christian could add a time line update for Aurora and Beta. | |||
=== | ===Installer Issues=== | ||
* There are some potential changes to the install process that Rob Strong discussed with Sayre yesterday. | |||
* | * The current plan is to install on top of. Some developers might want to install multiple versions and test their sites. Our plan will break that. | ||
* | * Rob Strong is going to send Jay an email to prep him on the issue. He will talk to Jay on Monday when he gets back from China. By Tues, we should be able to confirm the decision. | ||
* Probably need to have someone in product as part of these regular meetings - not the first issue that has come up. | |||