SUCCESS! [0:38:41.054860]
+1
On Thu, Nov 30, 2023 at 9:59 PM Nhat Nguyen
wrote:
> SUCCESS! [1:22:43.808415]
>
> +1
>
> On Thu, Nov 30, 2023 at 6:09 PM Christian Moen wrote:
>
>> SUCCESS! [1:49:26.873909]
>>
>> +1
>>
>> On Fri, Dec 1, 2023 at 3:09 AM Chris Hegarty
>> wrote:
>>
>>> Please vote
SUCCESS! [1:22:43.808415]
+1
On Thu, Nov 30, 2023 at 6:09 PM Christian Moen wrote:
> SUCCESS! [1:49:26.873909]
>
> +1
>
> On Fri, Dec 1, 2023 at 3:09 AM Chris Hegarty
> wrote:
>
>> Please vote for release candidate 2 for Lucene 9.9.0
>>
>>
>> The artifacts can be downloaded from:
>>
>>
>>
SUCCESS! [1:49:26.873909]
+1
On Fri, Dec 1, 2023 at 3:09 AM Chris Hegarty
wrote:
> Please vote for release candidate 2 for Lucene 9.9.0
>
>
> The artifacts can be downloaded from:
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
SUCCESS! [0:46:20.693134]
+1
On Thu, Nov 30, 2023 at 5:50 PM Tomás Fernández Löbbe
wrote:
> SUCCESS! [0:52:49.337126]
>
> +1
>
> On Thu, Nov 30, 2023 at 12:05 PM Benjamin Trent
> wrote:
>
>> SUCCESS! [0:44:05.132154]
>>
>> +1
>>
>> On Thu, Nov 30, 2023 at 1:09 PM Chris Hegarty
>> wrote:
>>
SUCCESS! [0:52:49.337126]
+1
On Thu, Nov 30, 2023 at 12:05 PM Benjamin Trent
wrote:
> SUCCESS! [0:44:05.132154]
>
> +1
>
> On Thu, Nov 30, 2023 at 1:09 PM Chris Hegarty
> wrote:
>
>> Please vote for release candidate 2 for Lucene 9.9.0
>>
>>
>> The artifacts can be downloaded from:
>>
>>
>>
Sounds like we could automate assigning the milestone, given that it is a
commonly forgotten step, based on the section of CHANGES where the PR gets
added?
I am pretty sure that I forgot to add entries to CHANGES too. That could be
maybe suggested in github. Whenever there's a PR that does not
Hopefully this is relevant.
There are useful tools like git-cliff for automating changelog generation.
https://github.com/orhun/git-cliff
Tony X
From: Michael McCandless
Sent: Thursday, November 30, 2023 4:30 AM
To: dev@lucene.apache.org
Subject: Re: GitHub
I just started a build with crave:
crave run ./gradlew --console=plain check integrationTests
And at the end of it, looked for the patterns in the crave pull command:
admin@171074329f9e:/tmp/src/solr$ find . -name '*.events'
admin@171074329f9e:/tmp/src/solr$ find . -name 'hs_err_pid*'
SUCCESS! [0:44:05.132154]
+1
On Thu, Nov 30, 2023 at 1:09 PM Chris Hegarty
wrote:
> Please vote for release candidate 2 for Lucene 9.9.0
>
>
> The artifacts can be downloaded from:
>
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
Investigating.
On Nov 26 2023, at 12:32 am, Mikhail Khludnev wrote:
> Pardon
>
> On Sun, Nov 26, 2023 at 11:28 AM Gautam Worah (mailto:worah.gau...@gmail.com)> wrote:
> > I think you meant to send it to d...@solr.apache.org
> > (mailto:d...@solr.apache.org)?
> >
> > On Sun, Nov 26, 2023 at
My expectation is that we will do a 9.x minor at about the same time as
10.0 anyway, this is what we have done in the past for new majors. This
will give an opportunity to make sure we have deprecation warnings for all
breaking changes in 10.0.
Le jeu. 30 nov. 2023, 10:43, Chris Hegarty
a écrit
> Thanks for raising the issue. I don’t have a strong opinion on whether or
not to do the deprecation in this release, and since you say that it is
minor, then I don’t see that it necessitates another respin. Since I had
already started an RC2 build, then I just continued with it (and since the
For clarity, consider this vote cancelled. A new vote has been started on an
RC2 build.
> On 30 Nov 2023, at 16:22, Greg Miller wrote:
>
> If we're spinning a new RC, I'd like to ask this group if it would make sense
> to pull this very small method deprecation in:
>
Please vote for release candidate 2 for Lucene 9.9.0
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC2-rev-06070c0dceba07f0d33104192d9ac98ca16fc500
You can run the smoke tester directly with this command:
python3 -u
OK, great. I wanted to post a +1 already. Will wait for 2nd RC.
Uwe
Am 30.11.2023 um 16:38 schrieb Michael McCandless:
On Thu, Nov 30, 2023 at 9:56 AM Chris Hegarty
wrote:
P.S. I’m less sure about this, but the RC 2 starts a 72hr voting
time again? (Just so I know what TTL to put on
If we're spinning a new RC, I'd like to ask this group if it would make
sense to pull this very small method deprecation in:
https://github.com/apache/lucene/pull/12854
If there's a chance we don't release a 9.10 and go directly to 10.0, this
would be our last opportunity to mark it deprecated on
for the sake of posterity, I did get a successful smoketest:
SUCCESS! [1:00:06.512261]
but +0 to release I guess since it's moot...
On Thu, Nov 30, 2023 at 10:38 AM Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Thu, Nov 30, 2023 at 9:56 AM Chris Hegarty
> wrote:
>
> P.S. I’m
On Thu, Nov 30, 2023 at 9:56 AM Chris Hegarty
wrote:
P.S. I’m less sure about this, but the RC 2 starts a 72hr voting time
> again? (Just so I know what TTL to put on that)
>
Yeah a new 72 hour clock starts with each new RC :)
Mike McCandless
http://blog.mikemccandless.com
Adrien,
> On 30 Nov 2023, at 14:51, Adrien Grand wrote:
>
> Yet another bug due to ghost fields. :( Thanks for fixing! For reference, I
> checked how postings work on SlowCompositeCodecReaderWrapper, since they are
> prone to ghost fields as well, and they seem to be ok.
Thanks for checking
Yet another bug due to ghost fields. :( Thanks for fixing! For reference, I
checked how postings work on SlowCompositeCodecReaderWrapper, since they
are prone to ghost fields as well, and they seem to be ok.
I worry that it could actually occur in practice when enabling recursive
graph bisection,
SUCCESS! [0:33:10.432870]
+1
On Thu, Nov 30, 2023 at 2:59 PM Chris Hegarty
wrote:
> Hi Mike,
>
> On 30 Nov 2023, at 11:41, Michael McCandless
> wrote:
>
> +1 to release.
>
> I hit a corner-case test failure and opened a PR to fix it:
> https://github.com/apache/lucene/pull/12859
>
>
> Good
Hi Mike,
> On 30 Nov 2023, at 11:41, Michael McCandless
> wrote:
>
> +1 to release.
>
> I hit a corner-case test failure and opened a PR to fix it:
> https://github.com/apache/lucene/pull/12859
Good find! It looks like the fix for this issue is well in hand - great.
> I don't think this
SUCCESS! [0:47:11.013106]
+1
On Thu, Nov 30, 2023 at 7:16 AM Ignacio Vera wrote:
> SUCCESS! [0:52:59.891964]
>
>
> +1
>
> On Thu, Nov 30, 2023 at 12:42 PM Michael McCandless <
> luc...@mikemccandless.com> wrote:
>
>> +1 to release.
>>
>> I hit a corner-case test failure and opened a PR to fix
Well, I created a starting tool to at least help us keep the
what-should-be-identical-yet-is-nearly-impossible-for-us-to-achieve
sections in CHANGES.txt in sync: https://github.com/apache/lucene/pull/12860
Right now it finds a number of mostly minor differences in the 9.9.0
sections in main vs
SUCCESS! [0:52:59.891964]
+1
On Thu, Nov 30, 2023 at 12:42 PM Michael McCandless <
luc...@mikemccandless.com> wrote:
> +1 to release.
>
> I hit a corner-case test failure and opened a PR to fix it:
> https://github.com/apache/lucene/pull/12859
>
> I don't think this should block the release?
+1 to release.
I hit a corner-case test failure and opened a PR to fix it:
https://github.com/apache/lucene/pull/12859
I don't think this should block the release? -- it looks exotic.
Thanks Chris!
Mike McCandless
http://blog.mikemccandless.com
On Thu, Nov 30, 2023 at 1:16 AM Patrick Zhai
I hit this one running the smoke tester on 9.9.0 RC 0, and it repros. I'll
open an issue ... I think it's just a missing null check in the
SlowCompositeCodecReaderWrapper.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Nov 28, 2023 at 6:37 PM Apache Jenkins Server <
27 matches
Mail list logo
