Awesome, thanks Steve for looking into it. This vote has passed, so I will start working on releasing this candidate. Thanks to all who voted.
Le lun. 13 févr. 2017 à 12:59, Steve Rowe <[email protected]> a écrit : Hi Adrien, This failure was addressed by SOLR-9088 and SOLR-9832, included in 6.2 & 6.4, respectively: ----- [smoker] [junit4] ERROR 13.9s J0 | TestManagedSchemaAPI.test <<< [smoker] [junit4] > Throwable #1: org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException: Error from server at http://127.0.0.1:44072/solr/testschemaapi_shard1_replica1: ERROR: [doc=2] unknown field 'myNewField1’ ----- This failure was AFAICT addressed by SOLR-9181 (since failures stopped happening on master/branch_6x after it was committed), included in 6.2: ----- [smoker] [junit4] ERROR 0.24s J1 | ZkStateReaderTest.testStateFormatUpdateWithExplicitRefresh <<< [smoker] [junit4] > Throwable #1: org.apache.solr.common.SolrException: Could not find collection : c1 ----- +1 to release 5.5.4 without backporting these fixes. -- Steve www.lucidworks.com > On Feb 13, 2017, at 4:10 AM, Adrien Grand <[email protected]> wrote: > > I would appreciate if someone could confirm that failures from https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.5/13/ are not release blockers. > > Le sam. 11 févr. 2017 à 06:31, Steve Rowe <[email protected]> a écrit : > +1 > > Changes, docs and javadocs look good, and the smoke tester was happy (with --test-java8): SUCCESS! [0:41:56.360623] > > -- > Steve > www.lucidworks.com > > > On Feb 8, 2017, at 3:28 PM, Adrien Grand <[email protected]> wrote: > > > > Le jeu. 9 févr. 2017 à 00:26, Adrien Grand <[email protected]> a écrit : > > Please vote for release candidate 1 for Lucene/Solr 6.4.1. > > > > I meant 5.5.4. > > > --------------------------------------------------------------------- > 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]
