I've backported and pushed SOLR-13285 to branch_8_0 (
https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=2ae4746). Ran all
tests and precommit.
Good luck, and hopefully this is it! Thank you once again for the patience,
Jim.
On Fri, Mar 8, 2019 at 12:59 AM jim ferenczi wrote:
> Thanks !
>
Thanks !
Le ven. 8 mars 2019 à 09:58, Anshum Gupta a écrit :
> I've back ported the commit. Just running the tests now and will commit as
> soon as the tests pass.
>
>
> On Fri, Mar 8, 2019 at 12:34 AM jim ferenczi
> wrote:
>
>> I agree, let's respin today and initiate a new vote. Do we have a
I've back ported the commit. Just running the tests now and will commit as
soon as the tests pass.
On Fri, Mar 8, 2019 at 12:34 AM jim ferenczi wrote:
> I agree, let's respin today and initiate a new vote. Do we have a
> volunteer for the backport or should I do it ?
>
> Le ven. 8 mars 2019 à
I agree, let's respin today and initiate a new vote. Do we have a volunteer
for the backport or should I do it ?
Le ven. 8 mars 2019 à 09:03, Adrien Grand a écrit :
> Since there is already a fix as Tomás mentioned, can someone backport
> it to branch_8_0 so that we can try to get a new RC out
.
Uwe
-
Uwe Schindler
Achterdiek 19, D-28357 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: u...@thetaphi.de
From: jim ferenczi
Sent: Thursday, March 7, 2019 5:53 PM
To: dev@lucene.apache.org
Subject: [VOTE] Release Lucene/Solr 8.0.0 RC3
Please vote for rele
Hi,
Sorry, but I also think that we should respin it if we can instead of
running a release of 8.0.1.
Kind Regards,
Furkan KAMACI
On Fri, Mar 8, 2019 at 10:24 AM Anshum Gupta wrote:
> Having done these releases more than a few times, I completely understand
> the frustration caused by such
Since there is already a fix as Tomás mentioned, can someone backport
it to branch_8_0 so that we can try to get a new RC out today?
@Ishan Chattopadhyaya No worry at all, thanks for taking care of
getting 7.7.1 out.
On Fri, Mar 8, 2019 at 8:24 AM Anshum Gupta wrote:
>
> Having done these
Having done these releases more than a few times, I completely understand
the frustration caused by such delays but I think that SOLR-13285 is
something that really breaks Solr in a major version release. We can always
have a 8.0.1 release that fixes it but I feel like it would not be a good
thing
In case we go through with this RC, I can volunteer to release a 8.0.1
(with SOLR-13285) immediately after 8.0.0 release.
@Adrien, Jim, I really understand the frustrations of an RM, and I also
apologize for the delay I caused to this release due to the intermediate
7.7.1 release where I didn't do
I understand the frustration with the delay and the number of respins, and
I don't want to be disrespectful of Jim's time as RC, but from what I can
see, SOLR-13285 would prevent anyone with enum fields to use Solr 8.0, and
the fix is already available.
-0
On Thu, Mar 7, 2019 at 2:14 PM Nhat
+1 SUCCESS! [0:54:05.261238]
> On Mar 7, 2019, at 4:44 PM, Adrien Grand wrote:
>
> +1 SUCCESS! [1:25:54.239684]
>
> On Thu, Mar 7, 2019 at 5:53 PM jim ferenczi wrote:
>>
>> Please vote for release candidate 3 for Lucene/Solr 8.0.0
>>
>> The artifacts can be downloaded from
>>
+1 SUCCESS! [1:25:54.239684]
On Thu, Mar 7, 2019 at 5:53 PM jim ferenczi wrote:
>
> Please vote for release candidate 3 for Lucene/Solr 8.0.0
>
> The artifacts can be downloaded from
>
It's not clear whether you are only asking for a backport or also for a respin.
I'm reluctant to respin: we built the first release candidate more
than 3 week ago now and have had to postpone it since then because of
late bugs. This is asking too much to the release manager in my
opinion. I am +1
I would like to backport SOLR-13285
On Fri, Mar 8, 2019 at 3:53 AM jim ferenczi wrote:
>
> Please vote for release candidate 3 for Lucene/Solr 8.0.0
>
> The artifacts can be downloaded from
>
Please vote for release candidate 3 for Lucene/Solr 8.0.0
The artifacts can be downloaded from
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.0.0-RC3-reva9d80bf18af04850ea21dcf88a40367559fb246e
You can run the smoke tester directly with this command:
python3 -u
15 matches
Mail list logo
