Hello,
I propose for 3.6 that we don't create a release branch but just use
our branch_3x as the release branch. We can 'svn mv' it to
'lucene_solr_3_6' when the release is ready.
Normally we would branch and open up branch_3x as 3.7 for changes, but
from previous discussions we intend to
I propose for 3.6 that we don't create a release branch but just use
our branch_3x as the release branch. We can 'svn mv' it to
'lucene_solr_3_6' when the release is ready.
Normally we would branch and open up branch_3x as 3.7 for changes, but
from previous discussions we intend to release
+1, makes my life easier
On Thu, Mar 22, 2012 at 7:51 AM, Martijn v Groningen
martijn.v.gronin...@gmail.com wrote:
I propose for 3.6 that we don't create a release branch but just use
our branch_3x as the release branch. We can 'svn mv' it to
'lucene_solr_3_6' when the release is ready.
+1. Keep it simple
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
On 22. mars 2012, at 12:48, Robert Muir wrote:
Hello,
I propose for 3.6 that we don't create a release branch but just use
our branch_3x as the release branch.
+1, much easier.
Tommaso
2012/3/22 Robert Muir rcm...@gmail.com
Hello,
I propose for 3.6 that we don't create a release branch but just use
our branch_3x as the release branch. We can 'svn mv' it to
'lucene_solr_3_6' when the release is ready.
Normally we would branch and open up
Robert,
I think this is a very good idea. +1.
Christian
http://atilika.com
On Mar 22, 2012, at 8:48 PM, Robert Muir wrote:
Hello,
I propose for 3.6 that we don't create a release branch but just use
our branch_3x as the release branch. We can 'svn mv' it to
'lucene_solr_3_6' when the
]
Sent: Thursday, March 22, 2012 12:48 PM
To: dev@lucene.apache.org
Subject: 3.6 branching
Hello,
I propose for 3.6 that we don't create a release branch but just use our
branch_3x as the release branch. We can 'svn mv' it to 'lucene_solr_3_6' when
the release is ready.
Normally we would
