> ** watch TBPL and back out the change if the build doesn't go green Having b2g developers to watch the tree for every cset we land on Aurora would involve a huge time and attention commitment. In particular, with infra turnaround times what they are, this severely limits the times of day when one can reasonably push to Aurora.
If we have many more pushes to Aurora (as we will, because we have hundreds of unresolved blocking-basecamp bugs), I'd expect the Aurora tree to burn more often, which makes it even more difficult to find an appropriate time to push. Moreover, just remembering to push every patch twice, separated by up to 12 hours, requires a large amount of mental energy. What would be really helpful, in my view, is if we could ask a sheriff to assist here. The sheriff could either land on Aurora himself, or could watch our pushes and basically do what m-i sheriffs do today. The former would be more useful than the latter, IMO. As I've said elsewhere, if we want to complete this project on time, particularly given the large recent increase in engineers, we should be asking less of developers, not more. This is a perfect example of that principal at work. -Justin On Mon, Oct 8, 2012 at 7:11 PM, Alex Keybl <[email protected]> wrote: >> Jonathan will need to move Nightly/Stable builds over to mozilla-aurora from >> mozilla-central for tonight's build, given the FF18 base. > > Actually, jgriffin may be on PTO today. Anybody else available to make this > change? > > -Alex > > On Oct 8, 2012, at 3:23 PM, Alex Keybl <[email protected]> wrote: > >> [re-sending, looks like formatting was dropped] >> >> Hi Ehsan, >> >> Just got done discussing this with drivers. Gecko 18 will be the basis for >> B2G v1 as things stand today. Here's how things will play out. >> >> >> = Landing Process until 11/19, or until told otherwise (mozilla-aurora 18) = >> * Land on mozilla-aurora (a=blocking-basecamp) if your landing: >> ** first landed on m-i/m-c and the build/tests are green >> ** has zero risk to the current desktop/mobile feature set and users (unused >> API, ifdef'd out, etc.) >> ** is blocking-basecamp+ >> ** does not have string/UUID changes >> >> * If your bug does not meet the above requirements (or if in doubt), mark >> the bug with approval-mozilla-aurora? as always and fill out the risk >> assessment. These are triaged as quickly as possible (every 1-2 weekdays). >> >> * Once landed on mozilla-aurora (standard stuff): >> ** mark status-firefox18:fixed >> ** paste the m-a hg link in the associated bug >> ** watch TBPL and back out the change if the build doesn't go green >> ** back out B2G changes on mozilla-aurora if backed out on mozilla-central >> for whatever reason >> >> * We will revoke the quick a=blocking-basecamp landing if it poses major >> risk to Aurora desktop/mobile users or if devs do not follow the guidelines >> above. At that point, all landings will first go through >> approval-mozilla-aurora? triage. >> >> >> = Landing Process after 11/19 (mozilla-beta 18) = >> * All landings will be required to go through approval-mozilla-beta? triage >> >> >> Jonathan will need to move Nightly/Stable builds over to mozilla-aurora from >> mozilla-central for tonight's build, given the FF18 base. Please let me know >> if anybody has questions about the above decisions or process. >> >> -Alex >> >> On Oct 2, 2012, at 10:47 AM, Ehsan Akhgari <[email protected]> wrote: >> >>> Hi all, >>> >>> Has there been a call on which version of Gecko b2g v1 will be based on? >>> We need to know whether we can backout bug 722845 on 18 after the uplift to >>> Aurora until we fix bug 787743 on trunk, and in order to make that call we >>> need to know whether b2g will be shipping off of Gecko 18 or trunk (which >>> will be Gecko 19 in about a week), since b2g depends on the work in bug >>> 722845. >>> >>> Thanks! >>> Ehsan >>> _______________________________________________ >>> 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 > > _______________________________________________ > 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
