Firefox:1.5.0.3:Release Team Notes:2006-03-15

2006-03-15

• Some key issues to consider:
  • The number of bugs is increasing dramatically each release
  • Should we have official release candidates for security releases?
  • How do we more reliably hit the code freeze date?
  • How do we deal with the increasing risk of last minute critical security bugs
  • How do we free up dveditz to do reviews (or at least module owner approvals) for security manager changes on trunk? [bz]

• Beyond issues we should talk about:
  • Rough schedule and milestones for 1.5.0.3
  • Revisit the criteria for bugs from 1.5.0.1

The 1.5.0.3 Kick-off meeting is planned for March 15, 2006, 11am PST

Dial-in:

   Toll-free Number:          866-432-7917
   International Number:    334-309-0297 

IRC #1503

Discussion:

• Top topics
  • Increasing ## of bugs
  • Schedule
  • Leadership/ dscision making
    • Rely on domain expert to make technical decisions
    • Make decision as mechanical as possible
    • Dan has his fill
    • Have published list of bugs to review
      • Who can nominate - used to be drivers/SG only in the past

• • • Who decides
      • Only drivers/SG can nominate?
      • problem with 1.5.02 was starting with >100 nomination
      • anyone can nominate <<==

• • • What is the turn-around time/who/quarum
      • No quarum - some obvious some not
      • Need to look at risk of nomination and risk of patch seperately
      • Definition for blcoking: branch managers should expend effort getting the fix in the release.
      • Appeals - re-nominate with addition

• • • what is the criteria
      • Not low risk fix allowed unless not FF relevant
      • What about JS spec bugs
      • How do we handle non-criteria issues
        • treat as exceptions - document why we excpeted it

• • • schedule for last nomination/NB approval
      • Stop accepting nominations/approval requestions - 5 days before
      • Or soft freeze and hard freeze [dbaron]
      • One final bug approval triage. Then onely triage landing approved bugs
        • 3 days
        • Only regresions from testing or bug sthat would cause an immediate re-release
        • Deadline

• • Bug criteria
• Dispersed
  • Communication
  • dev.planning, dev general
    • Not more than 4 news groups
  • set dates