Since we launched the Aurora channel on April 13th, 2011, we have been having twice weekly meetings to monitor feedback, stability, track issues and triage bugs. On Wednesday’s we come back for more and have a dedicated triage only session. In the beginning we spent far more time on the status part than the bug triage but this is shifting as we find our groove. Here are the highlights from today’s discussions.

• Communications
  • As we move faster, it’s been challenging to keep track of what decisions have been made and what the key problems are. How can we help?
  • We created this blog so we can centralize status updates, meeting summaries and channel related decisions.
  • The release-drivers list is used a lot and will continue to be used to handle the type of communications that it’s used for today.
• Meeting participation
  • A few issues have come up where we felt it would be important to have a product advocate to help us make some triage decisions. Until we have a dedicated Firefox product person to attend regularly, Sheila Mooney and Chris Blizzard will work together to make sure any feature issues that require product input are turned around quickly.
  • Since many of the bugs we triage are Fennec related, it’s important to have Fennec representation to help us triage them. Someone from the Fennec team will be attending the Wednesday triage session on a regular basis.
• Installer issues
  • There are 2 installer related issues that need to be resolved so we can finish the implementation. Bug 649594 and Bug649595.
  • Rob Strong is point for this and there is a meeting planned for Wed to come to a resolution.
• Aurora build frequency
  • The original plan was to build when a change has been made.
  • When we expanded this to include locale changes, it means that we would probably be building every night.
  • No change in plan but just noting that the builds will likely be nightly.

All the detailed meeting notes can be found on the Aurora wiki page.