Firefox3/StatusMeetings/2007-06-12: Difference between revisions

Firefox3/StatusMeetings/2007-06-12 (view source)

1,232 bytes removed , 13 June 2007

Confirmed users

1,067

edits

@@ Line 91: / Line 91: @@
 === General Discussion ===
-* Security Push
+* Security Triage Update
-** 1.9 Security Meeting Details (in direct email).
+* Textframe Enabled?
-** Definition of Security Push
-*** 49 and growing, security blockers we need to fix.
-*** Need to balance feature work and security efforts.
-*** If you feel your feature blockers are interfering with security blockers, need to help find another resource and/or specify that you are going to delay the release.
-*** Blocker security bugs have already been identified and you have at least a week to prepare for a week of security bug focus.
-*** Basic definition of Push:  Damon communicates your bug status <i>ad nauseam</i>.
-** A6 Security Push Week:  June 18-22.
-** B1 Security Push Week:  July 2-6.
-* Probably need to do the same for performance?
-* Triage Proposed Changes:
-** Move all triage meetings to a single day (monday?).
-** Make each triage meeting consecutive by functional group (i.e., GFX, Layout, Content, etc.).
-** Do not require everyone to attend everyone's triage sessions; however, one can sit through all of them if need be.
-** This will set expectation that triage will be completed at least once a week and we don't reach a point again between now and b1 where we have 192 existing noms.
-** damon, mconnor, schrep, and a few others will consider beginning daily triage sessions, as in Fx2.
 === Blockers and Noms ===