Working with a release branch makes sense if there is lot of activity
on the trunk, some of which may interfere with the release. That's not
the case; AFAICS all commits to the trunk are related to the release.
That means that using a release branch is just an unnecessary burden.

I think that the Synapse document is inspired by the Axis2 release
process [1], which still recommends creating a release as well, but
both Axis2 1.6.0 and 1.7.0 were released from the trunk. The last time
we used a release branch was for Axis2 1.5, and IIRC that was a
disaster because some of the changes on the release branch were not
applied to the trunk.

Andreas

[1] https://axis.apache.org/axis2/java/core/release-process.html

On Fri, Dec 30, 2016 at 1:15 AM, Ravi Undupitiya
<ravi.undupit...@gmail.com> wrote:
> Hi Andreas,
>
> I'm creating a branch for 3.0 release as per
> http://synapse.apache.org/dev/release-process.html
>
> On 30 December 2016 at 12:06, Andreas Veithen <andreas.veit...@gmail.com>
> wrote:
>>
>> Why?
>>
>> Andreas
>>
>> On Fri, Dec 30, 2016 at 12:59 AM,  <r...@apache.org> wrote:
>> > Author: ravi
>> > Date: Fri Dec 30 00:59:14 2016
>> > New Revision: 1776510
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1776510&view=rev
>> > Log:
>> > Creating 3.0 branch from current trunk
>> >
>> > Added:
>> >     synapse/branches/3.0/   (props changed)
>> >       - copied from r1776509, synapse/trunk/java/
>> >
>> > Propchange: synapse/branches/3.0/
>> >
>> > ------------------------------------------------------------------------------
>> > --- svn:ignore (added)
>> > +++ svn:ignore Fri Dec 30 00:59:14 2016
>> > @@ -0,0 +1,14 @@
>> > +*.iws
>> > +logs
>> > +.project
>> > +*.tmp
>> > +.settings
>> > +*.ipr
>> > +lib
>> > +.classpath
>> > +*.iml
>> > +target
>> > +bin
>> > +*.log
>> > +
>> > +projectFilesBackup
>> >
>> > Propchange: synapse/branches/3.0/
>> >
>> > ------------------------------------------------------------------------------
>> >     svn:mergeinfo = /synapse/branches/SYNAPSE-905:1384655-1389001
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
>> For additional commands, e-mail: dev-h...@synapse.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org

Reply via email to