Yeah, renaming the branch after release is a good idea. We should use the current 3.x branch to work on the release and there should be no 3.7 anymore. Techincally: branching 3.6 and deleting the branch_3x is not different in the sense of SVN to renaming (a rename is atomic copyadd + delete).
If we have major bugs in 3.6, we can still release 3.6.1, but this would be simply a new TAG in the 3.6 branch. Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Robert Muir [mailto:[email protected]] > Sent: Thursday, March 22, 2012 12:48 PM > To: [email protected] > 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 branch and open up branch_3x as 3.7 for changes, but from > previous discussions we intend to release 4.0 next (and put 3.x in maintenance > mode). > > As Hossman noted in his last email: we are doing some JIRA reorganization etc > to get things organized. Also related to this: > because we intend for this to be the last 3.x release, I want to make sure > people have a few more days to get their changes in. > > New features are fine, of course bugfixes, tests, and docs, but since we are > trying to get things in shape I only ask a few extra things at this stage: > * please ensure any new classes have at least one sentence as the class > javadocs > * please ensure any new packages have a package.html with at least a > description of what the package is > * please ensure any added files have the apache license header > > thoughts? objections? > > -- > lucidimagination.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
