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

Merge Tracking Tools / Tactics

From: Anderson, Aaron <AndersonA_at_gsicommerce.com>
Date: Wed, 10 Jun 2009 12:11:42 -0400

I'm interested in hearing what folks are doing to track the status of
merge jobs between branches in an environment with a lot of branches
running concurrently. Note that I am not talking about merge-tracking
of revisions, but rather that the merges are being run at all. So, for
example, let's say you have:


/software_component_x/trunk which is merging to:
/software_component_x/branches/release2, and


Now, lets say that you have human beings who are tasked with making sure
that the release1 branch is fully merged up from trunk before release1
goes live (and conversely with release2 and release3) and lets say that
you actually have a whole lot of branching going on like this and you
needed to construct a "dashboard" that reported back where one of those
humans may have missed doing a merge, particularly before a release goes
live. I realize you can do a svn mergeinfo --show-revs eligible across
all of them, but that doesn't scale well unless you start building a
database to track all outstanding branches with their sources they are
supposed to be taking merges from, which I'm hoping to avoid building.


Is there some tool out there that you can (putting on my simplistic hat
here) just point at a repo or series of repos and tell it what merges to
watch for and report back "up to dateness" of the merge jobs?


- Aaron Anderson



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-10 18:13:18 CEST

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