For those following along, here are the highlights from today’s Beta meeting.

• Schedule
  • Official cutover to Beta is May 17th, 2011.
  • Christian Legnitto will own communicating the timing of the merge and go to build. He will also log all the appropriate bugs to track everything that needs to be done.
  • There are 6 key bugs we are tracking that have to be dealt with prior to May 17th. The complete list is in the Aurora meeting notes. They will either be resolved or we will decide they are not severe enough to block the merge.
  • The go/no-go decision for doing the merge will happen in next week’s Beta meeting.
  • There is a subsequent decision to confirm that the Beta is in good shape to release after it undergoes the usual QA.
• Go/no-go decision
  • There is a set of information we need to assemble to make the go/no-go decision. This includes criteria like; stability, feedback, qa input, status of the 6 key tracking bugs.
  • QA will own assembling this data and present it during next week’s meeting so we can make the go/no-go decision.
• Beta user statistics
  • We now have about 37K users on 5.0b1.
  • Volume of users has been increasing on Beta and Aurora since the update went out last week.
  • Since we have not identified any big stability issues, we have decided to increase the throttle from 50% to 100% to offer the update to more users from the beta pool we are targeting.
  • We also decided that we would not stop at 100K users and see no reason not to offer this to all eligible users.
• Stability
  • We uncovered that 5.0 data was being throttled. While on the Beta channel, we want 100% of the crash reports. Socorro is fixing this issue. See bug 655838.
  • The numbers may look at bit strange in the meantime.
• Repository and mechanics
  • All ready to go for May 17th and no blocking issues.

As soon as we officially cutover 5.0 to the Beta channel, these meetings will include triage as well. The full notes are available here.