We can certainly hold back cutting the branch, and/or release. I'm headed to Berlin Buzzwords next week so I'd most probably be cutting the branch over the next weekend or during the conference. I'll keep everyone posted about the 'when' and if there are more contributors who want me to hold back for valid reasons, I'd be happy to do so :).
I'm tracking all blockers (and critical JIRAs) for 7.0, and if anyone thinks there's something that must be a part of 7.0, kindly mark the issue as a blocker for 7.0. -Anshum On Tue, May 30, 2017 at 9:27 AM Christine Poerschke (BLOOMBERG/ LONDON) < cpoersc...@bloomberg.net> wrote: > Hi Everyone, > > Just to say that https://issues.apache.org/jira/browse/SOLR-8668 for > <mergePolicy> removal should complete later this week, hopefully. > > And on an unrelated note, does anyone have any history or experience with > the NOTICE.txt files? Including > https://issues.apache.org/jira/browse/LUCENE-7852 in 7.0 would be good i > think (though it being a small change the issue would not need to block > branch_7x branch cutting). > > Thanks, > Christine > > From: dev@lucene.apache.org At: 05/03/17 16:56:09 > To: dev@lucene.apache.org > Subject: Re:Release planning for 7.0 > > Hi, > > It's May already, and with 6.6 lined up, I think we should start planning > on how we want to proceed with 7.0, in terms of both - the timeline, and > what it would likely contain. > > I am not suggesting we start the release process right away, but just > wanted to start a discussion around the above mentioned lines. > > With 6.6 in the pipeline, I think sometime in June would be a good time to > cut a release branch. What do all of you think? > > P.S: This email is about 'discussion' and 'planning', so if someone wants > to volunteer to be the release manager, please go ahead. I can't remember > if someone did explicit volunteer to wear this hat for 7.0. If no one > volunteers, I will take it up. > > -Anshum > >
