Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
(Created page with "=Development Policy for Stabilization Period= ==All bug activity will move to Bugzilla== * New Gaia bugs should be filed in Bugzilla, under the Boot2Gecko product and the Gaia ...") |
|||
| Line 19: | Line 19: | ||
** As we come closer to shipping, approval-gaia-master will be used for all landings (even if blocking+) | ** As we come closer to shipping, approval-gaia-master will be used for all landings (even if blocking+) | ||
==All commits require | ==Commit Changes== | ||
* All commits now require: | |||
** Unit or integration tests in the pull request or patch | |||
** A commit message format of "Bug {bugNumber} - {summary} (r={reviewer})", or at least have all of those components included. | |||
* Devs are expected to have run their tests locally before submitting any code changes for review, and including the test files in the pull request. | * Devs are expected to have run their tests locally before submitting any code changes for review, and including the test files in the pull request. | ||
* If your commit message doesn't | * If your commit message doesn't have all the required components, it will be backed out. The Gaia dev leads and the release drivers will be triaging the commit logs daily to ensure these requirements are followed. | ||
* Continuous integration + automated smoketests is being implemented at this moment and will be enabled as soon as possible. Once that happens, each and every commit will run all the tests and spit out a report letting you know if your change caused any test failures anywhere in the system. | * Continuous integration + automated smoketests is being implemented at this moment and will be enabled as soon as possible. Once that happens, each and every commit will run all the tests and spit out a report letting you know if your change caused any test failures anywhere in the system. | ||