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

Re: merge tracking use cases

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-12-01 02:36:59 CET

Daniel Rall wrote:
> On Fri, 30 Nov 2007, Mark Phippard wrote:
>> On Nov 30, 2007 5:59 PM, David Glasser <glasser@davidglasser.net> wrote:
>>> So, we have this merge tracking use cases/requirements doc:
>>> http://subversion.tigris.org/merge-tracking/requirements.html
>>> Which of these does current trunk (or "current trunk plus easy changes
>>> that we know how to do") support?
> Ignoring some bugs in what we do have, what we don't support fully
> includes:
> - Merging
> - The parts of Repeated Merge dealing with reflected/cyclic merging
> (issues #2897 and #2837)
> - Block/Unblock Changeset

I recall the discussion to defer blocking to 1.6, which I don't support, but
these two issues are the largest ones for the community in my mind. I still
suggest getting these into 1.5.

> - Parts of "Handle Renames" (some of which cmpilato has in progress)

Nice, but not as important as the above two, but then I don't do tons of
renaming and refactoring in my work.

While I understand we all want to get 1.5 out, it's going to be a long time (9+
months???) before 1.6 is close, unless we want to have a short 1.6 follow up, so
I'd rather see the most common needs handled in 1.5. The short release cycle I
recall, has met resistance due to the pain to our users and downstream packagers.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 1 02:37:30 2007

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.