> * Except under unusual circumstances, patches should be landing first on the > master branch, not a release branch like v1-train, v1.3, etc. If they need > to land on a release branch, they must go through the usual approval process > as outlined on the B2G Landing wiki page > (https://wiki.mozilla.org/Release_Management/B2G_Landing). Please take time > to familiarize yourself with this page if you haven't already done so and > bookmark it as we do our best to keep up-to-date with current information. > If you are a reviewer, *PLEASE* verify that the pull request was submitted > against the correct branch before granting r+.
Assuming it's not just me who messed this up recently, it might help new contributors to clarify the requirements for pull requests on the developer.mozilla.org docs. I was mostly following https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gaia/Hacking when trying to learn how to write & submit a patch. Even if I had found the B2G_Landing page, I doubt I would have known not to issue a pull request against v1-train. Since my phone is running v1.1, that's the branch I tried to build and test against. Just offering the perspective of someone not familiar with the B2G process :) Thanks, -Mike _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
