+1 SUCCESS! [1:31:37.834967]
(maybe non-binding)

And Luke works fine.

2019年7月21日(日) 21:52 Uwe Schindler <[email protected]>:
>
> Java 13 also worked.
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> https://www.thetaphi.de
>
> eMail: [email protected]
>
>
>
> From: Uwe Schindler <[email protected]>
> Sent: Sunday, July 21, 2019 2:49 PM
> To: [email protected]
> Subject: RE: [VOTE] Release Lucene/Solr 8.2.0 RC1
>
>
>
> Hi,
>
>
>
> I asked Policeman to run the smoke tester on my behalf, he responded:
>
>
>
> SUCCESS! [3:04:23.084427]
>
>
>
> (this was testing Java 8 and Java 9 module system). More details, see here: 
> https://jenkins.thetaphi.de/job/Lucene-Solr-Release-Tester/25/console
>
>
>
> I was also able to start Solr on Java 8 and Java 11 on Windows and index 
> example documents. I also analyzed some Korean text, all fine. I also tried 
> to run a custom plugin (query parsing and analysis) for one of my customers: 
> worked. As I did not recompile it, it verifies that the analysis factory 
> backwards break was prevented.
>
>
>
> So +1 to release this.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> https://www.thetaphi.de
>
> eMail: [email protected]
>
>
>
> From: Ignacio Vera <[email protected]>
> Sent: Friday, July 19, 2019 8:35 PM
> To: [email protected]
> Subject: [VOTE] Release Lucene/Solr 8.2.0 RC1
>
>
>
> Please vote for release candidate 1 for Lucene/Solr 8.2.0
>
>
>
> The artifacts can be downloaded from:
>
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.2.0-RC1-rev31d7ec7bbfdcd2c4cc61d9d35e962165410b65fe
>
>
>
> You can run the smoke tester directly with this command:
>
>
>
> python3 -u dev-tools/scripts/smokeTestRelease.py \
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.2.0-RC1-rev31d7ec7bbfdcd2c4cc61d9d35e962165410b65fe
>
> Here is my +1
>
> SUCCESS! [1:19:01.246595]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to