Thanks Uwe! Indeed we need branch_6x (and master versions changed) first. I'll plan to get that done Monday and/or Tuesday. Let me know if there are any blockers and I'll send a note to the list before I create the branch.
- Nick On Wednesday, February 24, 2016, Uwe Schindler <u...@thetaphi.de> wrote: > Hi Nicholas, > > > > before we start a branch_6_0 we should do the following: > > > > - Start branch_6x as “new stable branch” > > - Update version numbers in “master” to 7.0 > > > > This should be done maybe early next week and then after a while that > things settle (also the Jenkins Jobs for branch_6x are set up), we can > proceed with a gap: > > - Cut branch_6_0 > > - Update version numbers in “branch_6x” to 6.1 > > > > Uwe > > > > ----- > > Uwe Schindler > > H.-H.-Meier-Allee 63, D-28213 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaphi.de <javascript:_e(%7B%7D,'cvml','u...@thetaphi.de');> > > > > *From:* Nicholas Knize [mailto:nkn...@gmail.com > <javascript:_e(%7B%7D,'cvml','nkn...@gmail.com');>] > *Sent:* Wednesday, February 24, 2016 9:23 PM > *To:* Lucene/Solr dev <dev@lucene.apache.org > <javascript:_e(%7B%7D,'cvml','dev@lucene.apache.org');>> > *Subject:* Lucene/Solr 6.0.0 Release Branch > > > > With the release of 5.5 and the previous discussion re: 6.0.0 I'd like to > keep the ball moving and volunteer as the 6.0.0 RM. > > > > If there are no objections my plan is to cut branch_6_0 early next week - > Mon or Tues. Please mark blocker issues accordingly and/or let me know if > there are any commits needed before cutting the branch. > > > > - Nick >
