Please note that for any existing blocking-b2g:1.3+ bug you need to request an explicit approval on bugs to get them landed on the needed branch. Once a developer is certain that a patch is ready to be uplifted, please request approval-gaia-v1.3? or approval-mozilla-b2g28? on the attachment as appropriate. Fabrice/Release Management are going to go through these and once approved the sheriff will help land these on appropriate branch.
Please make sure to fill the below attachment form that pop's up on approval request: [Approval Request Comment] [Bug caused by] (feature/regressing bug #): [User impact] if declined: [Testing completed]: [Risk to taking this patch] (and alternatives if risky): [String changes made]: NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing#v1.3.0 to better understand the B2G approval process and landings. This change has been made to ensure the stability/quality of the 1.3 build and avoid any risky changes going in at this point. There is no change in terms of how security landings will happen. In addition, there is detailed discussion of the same topic on the b2g-internal list in case you are interested on more details about this change. Note, we are working on a plan for a well documented/determined path for 1.4 and on, and will keep you all posted on any change in the uplift strategy before 1.4 enters into the stabilization phase on March 17. Thanks, Bhavana P.S. hope I have all the needed lists to broadcast this info, feel free to forward add more if I missed any. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
