----- Original Message -----
> From: "Anthony Ricaud" <[email protected]>
> To: [email protected]
> Sent: Tuesday, June 10, 2014 6:02:38 AM
> Subject: Re: [b2g] m-c/master is now 2.1, 2.0 has branched
> 
> On 10/06/14 03:09, Bhavana Bajaj wrote:
> > =Until July 21th (next merge)=
> > * A bug will only land in v2.0 if it is marked with blocking-b2g:2.0+ or
> > the patch has gotten an exception through either
> > approval-mozilla-aurora+ or (Gecko) approval-gaia-v2.0+ (Gaia). Gaia
> > approval requests will not be encouraged after 7/7 and the bar to
> > approve bugs will get higher as we get towards the end of stabilization
> I thought there was a period where each functional team was responsible
> for managing uplifts at their own discretion. Was I dreaming or is it a
> change of policy for this cycle?

There is no change, this approval policy has existed on non-blocking bugs 
always :)
> 
> Also, do you have a link to a schedule of when those approval requests
> are looked at? In the past, I've had to actively reach out to people to
> get my approval in a timely manner (aka less than a week). This is
> slowing us down because we have duplicate bugs opened waiting for the
> uplift to happen.
Release management typically looks at approvals a couple of times a week. 
Sometimes we go back-forth on the approval request with folks, if all the 
details in the attachment form are not 
filled(https://wiki.mozilla.org/Release_Management/Uplift_rules), or we did not 
get the patch landed on master, or the patch isn't baked enough to shake out 
any obvious fallouts on a nightly if its risky, or we are waiting pending QA 
verification to get the confidence and uplift it on the branch.

If you have all the above and you still see a lag on acting on approvals NI : 
[email protected]/emailing us or a quick ping on irc is appreciated :)

--Bhavana
> 
> _______________________________________________
> dev-b2g mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-b2g
> 
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to