This is a summary of the most recent Aurora channel meeting:

Elevated crash level

• Christian wanted to talk about why Aurora seems to have a higher crash rate than both Nightly and Beta. We discussed at the last meeting and expected it to come down but it has not
• Christian pointed out that the oopsies / plugin hangs have come down since last meeting as expected (due to forward porting a fix from mozilla-central) but the Firefox crashes have trended up
• For crashes Bug 648022 still causing some residual issues according to smooney
  • For some unknown reason we started to see an increase in volume with this crash (~200 instead of ~40) around the same day as the backout on Aurora
  • The crashes appear for a build id prior to the backout
  • There are a couple of those showing in the latest build so we will continue to monitor this closely

• Those looking at crash stats should be aware Christian transplanted the JS PGO backout today – bug 605033
  • We don’t have any evidence that PGO raised the overall crash rate, it moved crashes around to different signatures. Turning it off until we understand more is a good idea
  • We will track turning it back on as a feature with a proper test plan. blizzard will own that feature

Growing Aurora audience, phase #1

• Asked for additional feedback on the previously announced plan
  • Decided phase 1 will continue
  • Potentially come up with more aggressive plan as some people don’t think Phase 1 is aggressive enough
  • Engagement is reluctant to spend their budget to promote Aurora right now. Asa will blog and write up a proposal to convince engagement to spend

Roundtable

• Axel would like to discuss the migration procedure once more, in particular closed branches vs no-op merges. Who would want to be on that thread?
  • Christian suggests the best place to talk about this will be in the rapid release post-mortem, next week time TBD
  • JP and joduinn suggested that the post-mortem isn’t the proper place as most people don’t care
    • Christian explained the first post-mortem will be used to identify issues that need to be spun off into their own post-mortem so we can deep-dive only on the areas we care about. People seemed satisfied with that
• JP suggested the use of beta next two weeks for Aurora confidence
  • There was some concern about the stability of Aurora
  • Decided it was a good idea to talk about and tabled it until Thursday’s meeting
• JP suggested we review tracking-firefox5+ bugs for tracking-firefox6+
  • Thought this was a good idea, decided it could wait for the next triage meeting
• There was discussion about the use of channels blog
  • Christian said he dropped the ball on posting meeting notes after smooney handed them off
  • Product marketing is supposed to come up with a coherent plan talking about what sort of information is posted where (channels, future releases, dev news, firefox blog, etc)
  • Grace asked if channels blog and dev news was even needed, everyone said as of right now yes

Action Items

• Asa to write a channels blog post about running different channels side-by-side
• Asa will blog and write up a proposal to convince engagement to spend for Aurora
• Christian will make sure notes get posted to the channels blog
• Christian will mass modify and email for outstanding Aurora patches