river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <bimargul...@gmail.com>
Subject Re: SVN and Jira
Date Mon, 16 Aug 2010 12:39:19 GMT
It's best to make sure that the merge does, in fact, carry all the comments
from the original in one big lump. svnmerge.py will do that for you
(aggregate the log comments from the merged branch into the merging commit),
as will git svn.

On Mon, Aug 16, 2010 at 8:27 AM, Jonathan Costers <
jonathan.costers@googlemail.com> wrote:

> Not 100% sure, but I would think one would have to mention the issue IDs
> again in the merge commit message.
>
> 2010/7/6 Tom Hobbs <tvhobbs@googlemail.com>
>
> > Any SVN/JIRA experts out there?
> >
> > Peter tells me that when he does a release any JIRA issues mentioned in
> the
> > SVN commit messages get listed in the release notes.  So how does this
> work
> > when merging onto the trunk from a skunk branch?
> >
> > For example, a developer commits to skunk/MyBranch and mentions JIRA
> issues
> > 123 and 456 in their commit messages.  But when the merge onto the trunk
> > happens, the "merge commit" message doesn't mention any JIRAs, or perhaps
> > it
> > only mentions issue 123.  My question is, when a release happens, is the
> > process clever enough to realise that it should list 123 and 456 in the
> > release notes, or will only the JIRA issues mentioned when the merge
> > happens
> > make their way into them?
> >
> > Thanks,
> >
> > Tom
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message