The Socorro folks have a bot which monitors github pull requests and comments in Bugzilla. Are we planning to set that up for Gaia?
Much more important than getting "r=someone" in the commit message is getting a bug number in the commit message. On mozilla-central, sheriffs usually won't back out a commit if someone forgets r=whoever, but they will back out the commit if someone puts the wrong bug number. -Justin On Fri, Sep 28, 2012 at 8:25 PM, Dietrich Ayala <[email protected]> wrote: > Hey everyone, > > Fantastic work this week - I've seen everyone hurtling towards feature > freeze, focusing on closing up as much of the work as possible. We're almost > ready to turn our focus entirely to cleanup, bug fixing and performance work. > This email will outline 1) the mechanics of the freeze itself and 2) the > workflow and commit policies after the freeze. > > NOTE: While most of the freeze and stabilization pieces are typical of > Mozilla release procedures, there will likely be tweaks as we iron out the > kinks - there are surely some gaps we'll have to fill in as we go. We'll > notify everyone of any changes as we move forward into this stage. If you > have questions, as always you can ask here, on the lists or to any of the > drivers directly. > > Feature Freeze Mechanics: > > 1. We'll allow check-ins to continue through the weekend, and will enact the > stabilization measures detailed below at midnight on Sunday. (UK/Europe's > Monday morning). Yes, you have the weekend to continue landing the last of > your feature work. However, as of 00:01 Monday PDT, you can no longer commit > code that does not meet the requirements detailed in the link below. > > 2. What about feature work that isn't done yet? There *is* feature work that > did not make the freeze. Some of it *will* land regardless. Those pieces are > all being tracked extremely closely, and drivers are being very very cautious > about what's accepted. Steps for requesting feature work to land after freeze > are detailed in the link below. We will be triaging remaining unimplemented > feature work, bug by bug, and determining if there's a market-specific reason > to assume the risk of allowing that development to land. > > Development Policy for Stabilization Period > > Please read at: https://wiki.mozilla.org/B2G/V1StabilizationPhase > > Biggest changes for Gaia developers, in summary: > > * All new bugs in Bugzilla during the stabilization phase. Go create an > account now if you don't have one. Our current set of blockers are being > migrated over there. Starting Monday, you'll live almost entirely in Bugzilla > for remaining V1 work. > > * All commits *must* have an attached unit/integration test. CI for these is > coming soon. > > * All commits/merges *must* have "r=ReviewerName". > > * Expect to be backed-out if you don't have the above in your pull requests. > > The details are all in the document above. > > (Tip: A while back I wrote a Firefox add-on for posting your Github pull > request to a Bugzilla bug. Usage: start the pull request title with "bug > xxxxxx" and the add-on will add a button to the Github UI for submitting it > as an attachment to that bug in Bugzilla. Use the 1.9 release: > https://addons.mozilla.org/en-US/firefox/addon/github-tweaks-for-bugzilla/versions/) > _______________________________________________ > 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
