The value of release bureaucracy
Posted Apr 19, 2012 18:40 UTC (Thu) by
BenHutchings (subscriber, #37955)
Parent article:
The value of release bureaucracy
The answer was simple: the rules for the stable tree do not allow the inclusion of any patch that has not already been merged, in some form, into the mainline.
This is not quite correct. If a patch goes into a stable branch and causes a regression there, but we know it doesn't cause that regression in mainline, then it is OK to revert it on the stable branch only (though in some cases it's better to cherry-pick the missed dependencies of the original patch from mainline). Also, a patch applied to the stable branch may sometimes look quite different from the corresponding patch(es) in mainline, but this is quite rare.
(
Log in to post comments)