Thx, I hope to create the first RC tomorrow. On Tue, Dec 1, 2015, at 06:36 PM, Noble Paul wrote: > I'm done with SOLR-8355 > > On Tue, Dec 1, 2015 at 4:24 PM, Noble Paul <[email protected]> wrote: > > hi Upayavira, > > sorry for the trouble. There is another blocker created > > https://issues.apache.org/jira/browse/SOLR-8355 > > I'm fixing that > > > > On Mon, Nov 30, 2015 at 8:26 PM, Christine Poerschke (BLOOMBERG/ > > LONDON) <[email protected]> wrote: > >> Fair point, I have re-worded the ticket title and summary. Will await > >> further opinions before applying or not applying the patch to 5.4 branch > >> (and trunk and branch_5x). > >> > >> Christine > >> > >> From: [email protected] At: Nov 30 2015 14:29:58 > >> To: [email protected] > >> Subject: Re: 5.4 branch created, feature freeze in place (was Re: A 5.4 > >> release?) > >> > >> The patch seems innocuous enough. From the ticket though it isn't so clear > >> to me what problem it solves. I'm open to the opinion of others. > >> > >> Upayavira > >> > >> On Mon, Nov 30, 2015, at 12:09 PM, Christine Poerschke (BLOOMBERG/ LONDON) > >> wrote: > >> > >> Any thoughts on getting the > >> https://issues.apache.org/jira/browse/LUCENE-6911 fix into 5.4 solr or not? > >> Basically StandardQueryParser's existing getMultiFields method is a no-op. > >> > >> From: [email protected] At: Nov 25 2015 14:11:46 > >> To: [email protected] > >> Subject: Re:5.4 branch created, feature freeze in place (was Re: A 5.4 > >> release?) > >> > >> I have created the lucene_solr_5_4 branch. Please, no new features in this > >> branch. > >> > >> Please update this thread with any changes you propose to make to this > >> branch. Only JIRA tickets which are a blocker and have fix version 5.4 will > >> delay a release candidate build. > >> > >> Please do review the below - and take any action to clear up these tickets > >> asap. > >> > >> I expect to create the first RC this time next week. > >> > >> Thanks! > >> > >> Upayavira > >> > >> On Wed, Nov 25, 2015, at 02:05 PM, Upayavira wrote: > >> > >> I shall shortly create the 5.4 release branch. From this moment, the > >> feature > >> freeze starts. > >> > >> Looking through JIRA, I see some 71 tickets assigned to fix version 5.4. I > >> suspect we won't be able to fix all 71 in one week, so I expect that the > >> majority will be pushed, after this release, to 5.5. > >> > >> Looking for blockers or critical tickets, I see five tickets: > >> > >> https://issues.apache.org/jira/browse/SOLR-8326 (Anusham, Noble) blocker > >> "Adding read restriction to BasicAuth + RuleBased authorization causes > >> issue with replication" > >> > >> Anusham/Noble - any thoughts on how to resolve this before the release? > >> > >> https://issues.apache.org/jira/browse/SOLR-8035 (Erik) critical > >> "Move solr/webapp to solr/server/solr-webapp" > >> > >> This one I know isn't a blocker in any sense. > >> > >> https://issues.apache.org/jira/browse/SOLR-7901 (Erik) critical > >> "Add tests for bin/post" > >> > >> Again, this one does not seem to be something worthy of holding back a > >> release > >> > >> https://issues.apache.org/jira/browse/LUCENE-6723 (Uwe) critical > >> "Date field problems using ExtractingRequestHandler and java 9 (b71)" > >> > >> Uwe, I presume as this relates to Java 9, it isn't a blocker? > >> > >> https://issues.apache.org/jira/browse/LUCENE-6722 (Shalin, others), blocker > >> "Java 8 as the minimum supported JVM version for branch_5x" > >> > >> Looking at the discussion, there was no consensus here, so I will not > >> consider this a blocker either. > >> > >> - o - > >> > >> So SOLR-8326 and LUCENE-6723 seem to be the ones worthy of attention. > >> Anyone > >> have comments/observations here? > >> > >> I will create the branch shortly. > >> > >> Upayavira > >> > >> > >> > >> > > > > > > > > -- > > ----------------------------------------------------- > > Noble Paul > > > > -- > ----------------------------------------------------- > Noble Paul > > --------------------------------------------------------------------- > 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]
