Merge Tracking Tools / Tactics

["Anderson, Aaron" <An...@gsicommerce.com>]

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/release1,
/software_component_x/branches/release2, and
/software_component_x/branches/release3

 

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

andersona@gsicommerce.com

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2360984

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: Merge Tracking Tools / Tactics

[Stefan Sperling <st...@elego.de>]

On Wed, Jun 10, 2009 at 12:11:42PM -0400, Anderson, Aaron wrote:
>    I'm interested in hearing what folks are doing to track the status of

Please don't start a new thread by replying to an existing one.

The message you sent had these headers:

  In-Reply-To:
  <D2...@eurmbx01.eur.adobe.com>
  References:
  <D2...@eurmbx01.eur.adobe.com>

which causes the list archives and various mail readers to sort your
messages as a reply to the following email, which has nothing to do
with yours: http://svn.haxx.se/users/archive-2009-06/0365.shtml

Please just take the the time to enter "users@subversion.tigris.org"
into the To: field in the future when posting a new question.

See also "Making a fresh post" under "Mailing List Etiquette"
on this page: http://subversion.tigris.org/mailing-lists.html

Thanks,
Stefan