[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [proposal] Handling of contested changes near release finalization

From: Karl Fogel <kfogel_at_google.com>
Date: 2006-09-06 00:17:51 CEST

Daniel Rall <dlr@collab.net> writes:
> If Mike expresses dissent to me about a change I'd made in trunk while
> we were walking towards Xebec (the bar near CollabNet), I'm not going
> to port the change to another branch until we've reached some sort of
> resolution, or at least continued discussion the following day (after
> coffee clears the haze of the pints ;). I've always assumed this was
> an unwritten understanding, but given the discussion on RC5 I've
> returned to after vacation, perhaps it is time to write it down?

In general I agree. But it's a continuum: what if you'd talked to 50
developers, and Mike was the only objector, and you knew you were
unlikely to ever persuade him? Then you'd probably just commit the

I'm not saying that's what happened here; I'm just saying this stuff
is a lot harder to formalize than it looks. The mere presence of
dissent becomes inevitable as the number of developers grows.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 6 00:18:49 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.