On Wed, Nov 04, 2015 at 03:00:52PM -0600, Robert Park wrote: > I've noticed recently that some people are force merging silos in > order to ignore problems with xenial-proposed migration while > continuing development in vivid.
> This is a Very Bad Thing as it causes xenial to rot, without anybody > paying attention or fixing it. More explicitly: the only person responsible for landing the package in xenial (as opposed to xenial-proposed) is the lander. A force-merge in the branch, in order to unblock development on trunk, means that *no one* has ownership for landing that package into xenial. It doesn't make it into the xenial image builds, it doesn't become part of the baseline that other landings are tested against. We need to make sure we're not dropping the ball on landings to trunk. Since the only use cases we have been able to think of for using force-merge are all exceptional, it seems reasonable to make this a landing-team-only operation. If you believe an exception is needed, you can talk to the landing team about doing a force-merge; but in the common case, we need to be making sure that packages land in xenial rather than stalling in xenial-proposed. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
