Confirmed users
4,971
edits
User:Asasaki:MBMerge: Difference between revisions
Jump to navigation
Jump to search
→No more dual-landing with bustage in between
| Line 33: | Line 33: | ||
** Landing one of these patches without the other results in tree bustage. It's difficult to time simultaneous landings; interdependent multi-repo landings are therefore riskier to land. | ** Landing one of these patches without the other results in tree bustage. It's difficult to time simultaneous landings; interdependent multi-repo landings are therefore riskier to land. | ||
** The fastest way to solve this is to merge mobile-browser in. | ** The fastest way to solve this is to merge mobile-browser in. | ||
=== Double- and triple- landings easier === | |||
* As we move further to a multiple project- and release- branch model, the chances of needing to double- or triple-land (or more) patches increases. | |||
** With mobile-browser merged in, this is double- or triple-landing | |||
** Without mobile-browser merged in, if the code affects both mobile-browser and platform, double- or triple-landing becomes quadruple- or sextuple-landing. | |||
=== Self-contained branches === | === Self-contained branches === | ||