canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,798
edits
(→Kats) |
MarkFinkle (talk | contribs) |
||
Line 11: | Line 11: | ||
== Major Topics for This Week == | == Major Topics for This Week == | ||
;Release Planning: We have been keeping an eye on the blocking bug counts, stability and performance metrics. The current plan was to uplift all required code to Aurora (Fx13) and ship a Beta to the marketplace 4/16+baketime. The adjusted plan (proposed) is to wait for Fx14 to merge to Aurora and ship a Beta to the marketplace 4/24+baketime. The only date adjustment is 4/16 to 4/24. Given the longer than usual beta period, we are not expecting to adjust the final release date at this time. | ;Release Planning: We have been keeping an eye on the blocking bug counts, stability and performance metrics. The current plan was to uplift all required code to Aurora (Fx13) and ship a Beta to the marketplace 4/16+baketime. The adjusted plan (proposed) is to wait for Fx14 to merge to Aurora and ship a Beta to the marketplace 4/24+baketime. The only date adjustment is 4/16 to 4/24. Given the longer than usual beta period, we are not expecting to adjust the final release date at this time. | ||
; Working on Soft Blockers: The release drivers may flas some blockers as "soft" meaning we'd take the fix if it makes the cut-off and is low-risk enough. Making the cut-off is an easy checkpoint, but determining low-risk is not. Even though drivers flag a bug as a soft blocker, we might still not accept the fix based on the risk level of the patch. The developer and review(s) need to chime in on the risk level. | |||
; Blocking Bug Disclaimer: Do not treat the blocking bug list as "these bugs must all be fixed before a beta candidate can be created" type of list. During blocking list cleanup, we have come across numerous bugs that would not really block if we had a beta candidate build that met our stability and performance criteria. | |||
==Stand ups== | ==Stand ups== |