On Dec 7, 2009, at 10:27 AM, Kalle Korhonen wrote:
On Mon, Dec 7, 2009 at 9:57 AM, Les Hazlewood
<[email protected]> wrote:
A big +1 from me.
I've been working this way for a while now and it has been really
nice thus far.
Agree - this is all according to Maven and svn best practices,
following release branching pattern (e.g.
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.commonpatterns.html)
.
Though I prefer naming branches with 1.x notation (rather than 1.0 or
1.1) since a branch often outlives the version and Maven makes it easy
to manage versions and branches. I'll see to it this happens. We can
move to 1.0.0-SNAPSHOT rather quickly, then we'll deal with the
remaining issues in the next few weeks and during the holidays, I can
go over the poms to see that we are ready to release.
If one uses a branch name branches/1.x and let's say that 1.0, 1.1,
and 1.2 have been released, what do you do when you need to patch
1.1? When you make this 1.x branch what goes into trunk?
Regards,
Alan
