To throw my 2 cents in on SOLR-13647. Yes, users can fix the problem trivially by updating their solr.in.sh _if_ they're aware of the issue. And we recommend all users examine their config carefully when upgrading Solr versions, so users _should_ be aware of the issue. But at the same time, the expectation/promise in previous releases has been that solr.in.sh has no effect (is entirely commented out) by default. So while we tell users to check all config files for themselves, we also tell them elsewhere that solr.in.sh is a bit of an exception out of the box. I think the "well the users should have checked" stance is a little simplistic in this case.
I wouldn't be against a respin, though I won't scuttle the vote if no one else feels strongly about it. But if there's no respin I think we should make an effort to highlight this potential issue either in the release announcement, release notes, or CHANGES.txt. Jason On Wed, Jul 24, 2019 at 9:36 AM Andrzej Białecki <[email protected]> wrote: > > +1 > > SUCCESS! [1:51:04.098987] > > > On 23 Jul 2019, at 14:01, Adrien Grand <[email protected]> wrote: > > > > +1 SUCCESS! [2:34:16.487011] > > > > > > On Fri, Jul 19, 2019 at 8:35 PM Ignacio Vera <[email protected]> wrote: > >> > >> 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] > > > > > > > > -- > > Adrien > > > > --------------------------------------------------------------------- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
