Firefox/Beta/2011-05-09: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 17: | Line 17: | ||
* According to crash stats, yesterday's volume on 5.0b1 was 37K. | * According to crash stats, yesterday's volume on 5.0b1 was 37K. | ||
* Over the weekend, getting about 11K hits on the first run page per day. | * Over the weekend, getting about 11K hits on the first run page per day. | ||
* Last Thurs/Fri, about 15K hits. | * Last Thurs/Fri, about 15K hits per day. | ||
* John: We have been running with 50% throttling so we didn't overshoot. Should we up that? | * John: We have been running with 50% throttling so we didn't overshoot. Should we up that? | ||
* We are going to go to 100% for that group of people. | ** We are going to go to change to 100% unthrottled for that group of people. | ||
* We | ** We will not stop at 100K users either; will offer to all ~417K eligible users. | ||
* | ** Details in {{bug|651982}} | ||
* | * Bump in numbers is en-US only - this is because FF5.0b1 is en-US only, not localized. | ||
* Bump in numbers | |||
==Stability report== | ==Stability report== | ||
Revision as of 21:41, 9 May 2011
Agenda
- Schedule
- Beta user stats
- Stability report
- Go/No Go decision
- Repo/mechanics
Schedule
- Official "Go To" Beta is still May 17th.
- The code that's in Aurora on the 16th, will move to Beta and we will do a build from there.
- The merge happens and we have the choice at that time whether or not the update is put out for all the beta users or not.
- We have 6 bugs we are tracking and we will either get them resolved or decide they are not severe enough to block.
- Laura: When will people see this beta live? Probably a couple of days after we do the merge. We will want some time to test this.
- Christian will work with Laura offline to figure out time line - log bugs for web pieces and everything that needs to happen when.
Beta user stats
- According to crash stats, yesterday's volume on 5.0b1 was 37K.
- Over the weekend, getting about 11K hits on the first run page per day.
- Last Thurs/Fri, about 15K hits per day.
- John: We have been running with 50% throttling so we didn't overshoot. Should we up that?
- We are going to go to change to 100% unthrottled for that group of people.
- We will not stop at 100K users either; will offer to all ~417K eligible users.
- Details in bug 651982
- Bump in numbers is en-US only - this is because FF5.0b1 is en-US only, not localized.
Stability report
- Top crash list similar to top crash list for Aurora.
- No new or explosive crashes have been identified.
- Still need more users on the channel.
- <Sheila to add more notes>
==Go/No Go
- Thread on the list
- What data would QA present to help us make the Go/No Go decisions.
- What has QA done up to that point.
- Stability report
- Performance? We don't have anybody reporting on this. Most of these should be handled in the Nightly to Aurora transition.
- Bugs we are tracking - 6 bugs.
- Go/No Go decision is about doing the merge.
- Matt owns packaging this up for Monday's meeting.
- Extension compatiblity - do we care about this? We probably can't make it part of the calculation for this time but in the future, this will be a bigger part of the criteria.
- Would we delay going to Beta if an extension is not compatible? Probably something we need to take to the list.
- 2 decisions: do a beta, did we do it correctly?
==Agenda
- Schedule
- Beta user stats
- Stability report
- Go/No Go decision
- Repo/mechanics
Schedule
- Official "Go To" Beta is still May 17th.
- The code that's in Aurora on the 16th, will move to Beta and we will do a build from there.
- The merge happens and we have the choice at that time whether or not the update is put out for all the beta users or not.
- We have 6 bugs we are tracking and we will either get them resolved or decide they are not severe enough to block.
- Laura: When will people see this beta live? Probably a couple of days after we do the merge. We will want some time to test this.
- Christian will work with Laura offline to figure out time line - log bugs for web pieces and everything that needs to happen when.
Beta user stats
- According to crash stats, yesterday's volume on 5.0b1 was 37K.
- Over the weekend, getting about 11K hits on the first run page per day.
- Last Thurs/Fri, about 15K hits.
- John: We have been running with 50% throttling so we didn't overshoot. Should we up that?
- We are going to go to 100% for that group of people.
- We probably don't need to stop at 100K users either.
- John: We have been running with 50% throttling so we didn't overshoot. Should we up that?
- We are going to go to 100% for that group of people.
- We probably don't need to stop at 100K users either.
- Bump in numbers for the different locales...some growth there.
Stability report
- Top crash list similar to top crash list for Aurora.
- No new or explosive crashes have been identified.
- Still need more users on the channel.
- <Sheila to add more notes>
Go/No Go
- Thread on the list
- What data would QA present to help us make the Go/No Go decisions.
- What has QA done up to that point.
- Stability report
- Performance? We don't have anybody reporting on this. Most of these should be handled in the Nightly to Aurora transition.
- Bugs we are tracking - 6 bugs.
- Go/No Go decision is about doing the merge.
- Matt owns packaging this up for Monday's meeting.
- Extension compatiblity - do we care about this? We probably can't make it part of the calculation for this time but in the future, this will be a bigger part of the criteria.
- Would we delay going to Beta if an extension is not compatible? Probably something we need to take to the list.
Repo/Mechanics
- Still an issue with l10n but it doesn't affect the merge on May 17th. This would relate to the next merge from Aurora-Beta.