Firefox:1.5.0.2:Meeting Notes

Revision as of 19:03, 27 February 2006 by GavinSharp (talk | contribs) (bugify links)

Notes about these notes

  • Firefox 1.5.0.2 discussions of non-security-sensitive bugs are recorded on this page
    • Discussions regarding security-sensitive bugs are recorded on the internal security wiki
    • see http://www.mozilla.org/projects/security/ for public information about security issues
    • This page is not a channel to request or announce information about specific security-sensitive bugs
  • Updates to this page should come from attendees of the Firefox 1.5.0.2 meetings
  • If you disagree with the decision of the triage committee about a specific bug, please present your case in the comments for that bug

Notes

(2006-02-06) Pre-meeting Bug Stats

(2006-02-07) Triage meeting

(2006-02-08) Triage meeting

(2006-02-09) Triage meeting

(2006-02-27) Update

  • I apologize for not keeping these notes up to date
  • I'm going through the Firefox bugs marked fixed1.8.0.2 and adding pseudo-flags to the status whiteboard in the format [xxx-dl]
    • [rft-dl] - ready for testing - ready for qa to verify the fix
    • [tcn-dl] - test case needed - need more info to verify the fix
    • [tjp-dl] - test japan - need to ask mozilla japan folks to help verify
    • [nvn-dl] - no verification needed - I think we can skip directed/focused verification of this bug. Usually because:
      • this is an internal architecture change and we're just looking for anything else that breaks
      • this fixes a topcrasher, and we'll look at the topcrash stats after release to make sure the crash frequency goes down
      • build/packaging issue (like building univeral binaries for macos, or BeOS-only changes) - if the builds exist and run, the patch is ok
      • covered by testing we do anyway. Some software update changes are covered by this flag
  • As always, let me and/or drivers know if you disagree with a flag. I'm very willing to change my mind when presented with new information.
  • Our goal is to verify all critical security fixes, and 60% of all fixes overall, before releasing 1.5.0.2