13 06:08
> To: Gavin Baumanis; users@subversion.apache.org
> Subject: RE: Merging change sets for a production release,
>
>
>
> > -Original Message-
> > From: Gavin Baumanis [mailto:gbauma...@cogstate.com]
> > Sent: Monday, June 03, 2013 2:27 PM
> > To:
Guten Tag Gavin Baumanis,
am Montag, 3. Juni 2013 um 20:26 schrieben Sie:
> As for the other ideas, we do already only merge changes from trunk
> that are complete and have been given the appropriate release milestone.
> Our release process is already issue-based.
This alone won't help you. How m
> -Original Message-
> From: Gavin Baumanis [mailto:gbauma...@cogstate.com]
> Sent: Monday, June 03, 2013 2:27 PM
> To: Andrew Reedick; users@subversion.apache.org
> Subject: RE: Merging change sets for a production release,
>
> Hi Andrew,
> Thanks for
.
Perhaps simply chaining the merge revisions is the answer?
> -Original Message-
> From: Andrew Reedick [mailto:andrew.reed...@cbeyond.net]
> Sent: Tuesday, 4 June 2013 00:48
> To: Gavin Baumanis; users@subversion.apache.org
> Subject: RE: Merging change sets for a pro
> -Original Message-
> From: Gavin Baumanis [mailto:gbauma...@cogstate.com]
> Sent: Monday, June 03, 2013 12:31 AM
> To: users@subversion.apache.org
> Subject: Merging change sets for a production release,
> Importance: High
>
> At the moment we do all of our work on /trunk and also have
On Jun 3, 2013 12:27 PM, "Gavin Baumanis" wrote:
>
> Hi Everyone,
>
> At the moment we do all of our work on /trunk and also have
/branches/releases/1.0
> When we have enough issues, we mark the ready / required issues with a
new release milestone and I go about the task of merging the required
ch
