canmove, Confirmed users, Bureaucrats and Sysops emeriti
1,334
edits
Tree Rules/Integration: Difference between revisions
Jump to navigation
Jump to search
→What are the tree rules for mozilla-inbound?: clarify that test before pushing doesn't mean full try run for every patch
m (→Meet the Sheriffs: Add mistakenly removed Ms2ger) |
(→What are the tree rules for mozilla-inbound?: clarify that test before pushing doesn't mean full try run for every patch) |
||
| Line 12: | Line 12: | ||
** Committers are ''not'' required to actively watch the tree after pushing to mozilla-inbound. | ** Committers are ''not'' required to actively watch the tree after pushing to mozilla-inbound. | ||
** Checking tinderbox before pushing is not required, but it is appreciated. If the tree is in a very broken state, you can save the sheriffs work by notifying them instead of pushing. | ** Checking tinderbox before pushing is not required, but it is appreciated. If the tree is in a very broken state, you can save the sheriffs work by notifying them instead of pushing. | ||
* Inbound is no replacement for '''[[Try]]'''. You still need to test your patches before pushing. | * Inbound is no replacement for '''[[Try]]'''. You still need to test your patches before pushing. (This doesn't mean that you need an all-platforms try run for every patch. But it does mean that you should do enough testing so that you rarely cause red or orange on mozilla-inbound. But breaking it rarely is ok. Never missing a plane means you're spending too much time in airports; never breaking the tree means you're running too many tests before landing.) | ||
* When can I push to mozilla-inbound? '''Always!''' | * When can I push to mozilla-inbound? '''Always!''' | ||
** If there is something very wrong with mozilla-inbound, a sheriff will close the tree, and your push will fail automatically. | ** If there is something very wrong with mozilla-inbound, a sheriff will close the tree, and your push will fail automatically. | ||