Re: [JENKINS] Lucene » Lucene-Artifacts-main - Build # 391 - Still Failing!

2021-10-15 Thread Dawid Weiss
I corrected Jenkins job definition to run "assembleRelease" and to
collect artifacts from the right location
(lucene/distribution/build/release/**).

On Fri, Oct 15, 2021 at 12:36 AM Apache Jenkins Server
 wrote:
>
> Build: https://ci-builds.apache.org/job/Lucene/job/Lucene-Artifacts-main/391/
>
> No tests ran.
>
> Build Log:
> [...truncated 316 lines...]
> ERROR: Step ‘Archive the artifacts’ failed: No artifacts found that match the 
> file pattern "lucene/packaging/build/distributions/**". Configuration error?
> Publishing Javadoc
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
>
> -
> To unsubscribe, e-mail: builds-unsubscr...@lucene.apache.org
> For additional commands, e-mail: builds-h...@lucene.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: should we clean up dev-docs?

2021-10-15 Thread Dawid Weiss
> We also have the help/ folder which is plaintext since it can be invoked with 
> ./gradlew helpXXX. Someone should decide what goes in help/ vs dev-docs/

In all honesty, I prefer plain text files, much in the spirit of RFC
documents. They work well, they display well on all known terminals
and they don't require any added knowledge of N different flavors of
markup formatting languages. I know some of you may disagree but it's
not going to change my mind on the subject - sorry for being
old-fashioned.

D.

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

2021-10-15 Thread Tomás Fernández Löbbe
+1

SUCCESS! [1:11:35.593338]

On Fri, Oct 15, 2021 at 11:41 AM Anshum Gupta 
wrote:

> +1 (binding)
>
> Smoke tester passed w/ JDK 8.
>
> SUCCESS! [1:18:04.585401]
>
> Also tried a basic app w/ indexing and search and everything I tested
> worked as expected.
>
> Thanks for doing this, Mayya!
>
> On Tue, Oct 12, 2021 at 5:00 PM Mayya Sharipova  wrote:
>
>> Please vote for release candidate 1 for Lucene/Solr 8.10.1
>>
>> The artifacts can be downloaded from:
>>
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
>>
>> 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.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
>>
>> The vote will be open for at least 72 hours i.e. until 2021-10-15 23:00
>> UTC.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1 : SUCCESS! [1:07:19.906103]
>> 
>>
>
>
> --
> Anshum Gupta
>


Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

2021-10-15 Thread Anshum Gupta
+1 (binding)

Smoke tester passed w/ JDK 8.

SUCCESS! [1:18:04.585401]

Also tried a basic app w/ indexing and search and everything I tested
worked as expected.

Thanks for doing this, Mayya!

On Tue, Oct 12, 2021 at 5:00 PM Mayya Sharipova  wrote:

> Please vote for release candidate 1 for Lucene/Solr 8.10.1
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
>
> 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.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
>
> The vote will be open for at least 72 hours i.e. until 2021-10-15 23:00
> UTC.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1 : SUCCESS! [1:07:19.906103]
> 
>


-- 
Anshum Gupta


Re: should we clean up dev-docs?

2021-10-15 Thread Jan Høydahl
A cleanup is needed. One dev-docs folder is enough now :) 
We also have the help/ folder which is plaintext since it can be invoked with 
./gradlew helpXXX. Someone should decide what goes in help/ vs dev-docs/

Asciidoc is more capable than MD, and renders well in GitHub as well: 
https://github.com/apache/lucene/blob/main/dev-docs/pmc-chair.adoc
I think there may be some future idea to compile dev-docs into some dev guide 
online, if so, adoc will make it much easier to cross-link, add images, tables  
etc.

Jan

> 15. okt. 2021 kl. 16:51 skrev Adrien Grand :
> 
> I suspect that the adoc format got used because it was the format that was 
> already being used for the Solr ref guide. +1 to move to Markdown.
> 
> 
> 
> On Fri, Oct 15, 2021 at 3:49 PM Michael Sokolov  > wrote:
> I was poking around looking for info on how we release Lucene, and I
> stumbled into this dev-docs folder. It seems to have info that's
> mostly useful for solr workflows, assumes you are working in
> lucene-solr repo, etc. The info about pmc-chair seems helpful, and
> maybe Putnam's guide to using git worktree, which was new to me, but
> the rest should probably go / get updated to refer to lucene repo.
> 
> One question I have is about this adoc format - is it processed by
> something and published somewhere, or is this just intended to be read
> in the source tree (or maybe on github). If it's the latter, maybe we
> should switch to markdown?
> 
> Also, I did find the dev-tools folder and the release wizard. The
> README.md in there is very helpful. I wonder if we ought to simply
> consolidate the docs in dev-docs in here so they are easier to
> discover together?
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org 
> 
> For additional commands, e-mail: dev-h...@lucene.apache.org 
> 
> 
> 
> 
> -- 
> Adrien



Re: Lucene 9.0 release

2021-10-15 Thread Timothy Potter
Sounds like a good plan Adrien, thanks for nailing down some concrete
milestones and dates :-)

Cheers,
Tim

On Fri, Oct 15, 2021 at 7:04 AM David Smiley  wrote:
>
> +1 Adrien.  Thanks for moving things along.
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
> http://www.linkedin.com/in/davidwsmiley
>
>
> On Fri, Oct 15, 2021 at 3:30 AM Adrien Grand  wrote:
>>
>> For visibility, I recently opened a new issue about a case of index 
>> corruption which is a blocker for 9.0. Nhat is looking into it.
>>
>> We've been discussing releasing 9.0 for a long time now and I think that 
>> everybody agrees with moving forward, there's even some good momentum around 
>> making the build and release tooling ready. So I'd like to propose the 
>> following timeline for the 9.0 release to get some feedback:
>>
>> 2021-11-01: Feature freeze:
>>  - branch_9x gets created from main
>>  - branch_8_11 gets created from branch_8x
>> This gives us ~2 weeks to do some last-minute work. The reasoning for doing 
>> 8.11 as well is that we have some enhancements merged to branch_8x that I 
>> suspect some users would like to see released in 8.x. Important note: 8.11 
>> will be the last minor release of major version 8. There might be new patch 
>> releases in the future such as 8.11.1 or 8.11.2, but there won't be a 8.12 
>> or a 8.13.
>>
>> 2021-11-04: First RC for 8.11
>> Since we had 8.10 not long ago, hopefully the release process will go 
>> smoothly.
>>
>> ~2021-11-10: First RC for 9.0
>> The date is indicative, the plan would be to move forward with the first 9.0 
>> RC as soon as the following conditions are met:
>>  - 8.11 is out
>>  - all 9.0 blockers have been addressed
>>
>> Mike, your previous email suggests that you would like someone else to step 
>> up. If that's correct I'm happy to be the release manager for both 8.11 and 
>> 9.0.
>>
>>
>> On Sat, Oct 2, 2021 at 11:54 PM Michael Sokolov  wrote:
>>>
>>> Yes! I'm curious to give it a go, but getting pulled in many different
>>> directions. If nobody else steps up, I will be free to shepherd the
>>> release along in a  couple of weeks, assuming the current firestorm
>>> subsides...
>>>
>>> On Thu, Sep 30, 2021 at 9:54 AM Jan Høydahl  wrote:
>>> >
>>> > +1
>>> >
>>> > Blockers seem to be done with. So I guess we just need an RM to get the 
>>> > ball rolling? :)
>>> >
>>> > I know that the Release Wizard in new Lucene repo needs some updates 
>>> > https://issues.apache.org/jira/browse/LUCENE-9809 - I may help some with 
>>> > that...
>>> >
>>> > Cross-ref other 9.0 release mail-threads:
>>> > - "Now that 8.10 is out ... let's get rolling on 9!" 
>>> > https://lists.apache.org/thread.html/r868028d42a19ae02d5bbe2e3329da26869045002b9bb4760b8056c56%40%3Cdev.lucene.apache.org%3E
>>> > - "9.0 release": 
>>> > https://lists.apache.org/thread.html/r7bef0af668860fdbfedb4b58261efd01d9fb26dc280915284c121065%40%3Cdev.lucene.apache.org%3E
>>> >
>>> > Jan
>>> >
>>> > 17. aug. 2021 kl. 11:13 skrev Adrien Grand :
>>> >
>>> > +1 to your suggestions
>>> >
>>> > I just commented on LUCENE-9959 to suggest reverting since the changes 
>>> > are currently half baked and I don't think that they should block 9.0. 
>>> > There are no other blockers left to my knowledge.
>>> >
>>> > On Sat, Aug 14, 2021 at 6:24 PM Michael Sokolov  
>>> > wrote:
>>> >>
>>> >> It's been two years since our last release, we had lots of +1 when we
>>> >> raised this last December, and IMO we are close to baked at this
>>> >> point.
>>> >>
>>> >> I checked JIRA and found two remaining Blockers
>>> >>
>>> >> 1. https://issues.apache.org/jira/browse/LUCENE-10016
>>> >> VectorReader.search needs rethought, o.a.l.search integration?
>>> >> 2. https://issues.apache.org/jira/browse/LUCENE-8638 Remove deprecated
>>> >> code in main
>>> >>
>>> >> The first one is very close to resolved;
>>> >>
>>> >> On the deprecations, the issue has lingered for 1-1/2 years now, and
>>> >> some progress has been made, but more work remains. Some new
>>> >> deprecations have been added since it was opened too. Maybe we make a
>>> >> concerted effort to clean out as much as we can, and then decide if
>>> >> it's enough? Anyway this seems to be the only outstanding issue, so
>>> >> let's see if we can make progress there
>>> >>
>>> >> Q: any other blockers?
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> >> For additional commands, e-mail: dev-h...@lucene.apache.org
>>> >>
>>> >
>>> >
>>> > --
>>> > Adrien
>>> >
>>> >
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>
>>
>> --
>> Adrien

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

2021-10-15 Thread Atri Sharma
+1

SUCCESS! [1:28:35.594227]

On Fri, Oct 15, 2021 at 9:48 PM Michael Sokolov  wrote:
>
> +1 SUCCESS! [1:11:55.023477]
>
> I blame some random antivirus or something kicking in at the same time
>
> On Fri, Oct 15, 2021 at 10:44 AM Michael Sokolov  wrote:
> >
> > having a little trouble here with new laptop - after installing jdk8,
> > ant, and finally running the smoke tester - my laptop shut down due to
> > overheating! A little afraid to try it again, but I'll try improving
> > the air circulation ...
> >
> > On Thu, Oct 14, 2021 at 2:53 PM Namgyu Kim  wrote:
> > >
> > > +1 SUCCESS! [1:00:57.143976]
> > >
> > > On Fri, Oct 15, 2021 at 1:05 AM Houston Putman  wrote:
> > >>
> > >> +1 SUCCESS! [1:05:55.854939]
> > >>
> > >> On Thu, Oct 14, 2021 at 9:29 AM Michael Gibney 
> > >>  wrote:
> > >>>
> > >>> +1 SUCCESS! [1:00:31.099832]
> > >>>
> > >>> On Thu, Oct 14, 2021 at 7:42 AM Ignacio Vera  wrote:
> > 
> >  +1
> > 
> >  SUCCESS! [1:01:50.808390]
> > 
> > 
> >  On Thu, Oct 14, 2021 at 1:40 PM Michael McCandless 
> >   wrote:
> > >
> > > +1
> > >
> > >
> > > SUCCESS! [0:44:35.590557]
> > >
> > >
> > > Mike McCandless
> > >
> > > http://blog.mikemccandless.com
> > >
> > >
> > > On Tue, Oct 12, 2021 at 8:00 PM Mayya Sharipova  
> > > wrote:
> > >>
> > >> Please vote for release candidate 1 for Lucene/Solr 8.10.1
> > >>
> > >> The artifacts can be downloaded from:
> > >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
> > >>
> > >> 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.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
> > >>
> > >> The vote will be open for at least 72 hours i.e. until 2021-10-15 
> > >> 23:00 UTC.
> > >>
> > >> [ ] +1  approve
> > >> [ ] +0  no opinion
> > >> [ ] -1  disapprove (and reason why)
> > >>
> > >> Here is my +1 : SUCCESS! [1:07:19.906103]
> > >> 
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>


-- 
Regards,

Atri
Apache Concerted

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

2021-10-15 Thread Michael Sokolov
+1 SUCCESS! [1:11:55.023477]

I blame some random antivirus or something kicking in at the same time

On Fri, Oct 15, 2021 at 10:44 AM Michael Sokolov  wrote:
>
> having a little trouble here with new laptop - after installing jdk8,
> ant, and finally running the smoke tester - my laptop shut down due to
> overheating! A little afraid to try it again, but I'll try improving
> the air circulation ...
>
> On Thu, Oct 14, 2021 at 2:53 PM Namgyu Kim  wrote:
> >
> > +1 SUCCESS! [1:00:57.143976]
> >
> > On Fri, Oct 15, 2021 at 1:05 AM Houston Putman  wrote:
> >>
> >> +1 SUCCESS! [1:05:55.854939]
> >>
> >> On Thu, Oct 14, 2021 at 9:29 AM Michael Gibney  
> >> wrote:
> >>>
> >>> +1 SUCCESS! [1:00:31.099832]
> >>>
> >>> On Thu, Oct 14, 2021 at 7:42 AM Ignacio Vera  wrote:
> 
>  +1
> 
>  SUCCESS! [1:01:50.808390]
> 
> 
>  On Thu, Oct 14, 2021 at 1:40 PM Michael McCandless 
>   wrote:
> >
> > +1
> >
> >
> > SUCCESS! [0:44:35.590557]
> >
> >
> > Mike McCandless
> >
> > http://blog.mikemccandless.com
> >
> >
> > On Tue, Oct 12, 2021 at 8:00 PM Mayya Sharipova  
> > wrote:
> >>
> >> Please vote for release candidate 1 for Lucene/Solr 8.10.1
> >>
> >> The artifacts can be downloaded from:
> >> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
> >>
> >> 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.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
> >>
> >> The vote will be open for at least 72 hours i.e. until 2021-10-15 
> >> 23:00 UTC.
> >>
> >> [ ] +1  approve
> >> [ ] +0  no opinion
> >> [ ] -1  disapprove (and reason why)
> >>
> >> Here is my +1 : SUCCESS! [1:07:19.906103]
> >> 

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: should we clean up dev-docs?

2021-10-15 Thread Adrien Grand
I suspect that the adoc format got used because it was the format that was
already being used for the Solr ref guide. +1 to move to Markdown.



On Fri, Oct 15, 2021 at 3:49 PM Michael Sokolov  wrote:

> I was poking around looking for info on how we release Lucene, and I
> stumbled into this dev-docs folder. It seems to have info that's
> mostly useful for solr workflows, assumes you are working in
> lucene-solr repo, etc. The info about pmc-chair seems helpful, and
> maybe Putnam's guide to using git worktree, which was new to me, but
> the rest should probably go / get updated to refer to lucene repo.
>
> One question I have is about this adoc format - is it processed by
> something and published somewhere, or is this just intended to be read
> in the source tree (or maybe on github). If it's the latter, maybe we
> should switch to markdown?
>
> Also, I did find the dev-tools folder and the release wizard. The
> README.md in there is very helpful. I wonder if we ought to simply
> consolidate the docs in dev-docs in here so they are easier to
> discover together?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Adrien


Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

2021-10-15 Thread Michael Sokolov
having a little trouble here with new laptop - after installing jdk8,
ant, and finally running the smoke tester - my laptop shut down due to
overheating! A little afraid to try it again, but I'll try improving
the air circulation ...

On Thu, Oct 14, 2021 at 2:53 PM Namgyu Kim  wrote:
>
> +1 SUCCESS! [1:00:57.143976]
>
> On Fri, Oct 15, 2021 at 1:05 AM Houston Putman  wrote:
>>
>> +1 SUCCESS! [1:05:55.854939]
>>
>> On Thu, Oct 14, 2021 at 9:29 AM Michael Gibney  
>> wrote:
>>>
>>> +1 SUCCESS! [1:00:31.099832]
>>>
>>> On Thu, Oct 14, 2021 at 7:42 AM Ignacio Vera  wrote:

 +1

 SUCCESS! [1:01:50.808390]


 On Thu, Oct 14, 2021 at 1:40 PM Michael McCandless 
  wrote:
>
> +1
>
>
> SUCCESS! [0:44:35.590557]
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Oct 12, 2021 at 8:00 PM Mayya Sharipova  wrote:
>>
>> Please vote for release candidate 1 for Lucene/Solr 8.10.1
>>
>> The artifacts can be downloaded from:
>> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
>>
>> 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.10.1-RC1-rev2f24e6a49d48a032df1f12e146612f59141727a9
>>
>> The vote will be open for at least 72 hours i.e. until 2021-10-15 23:00 
>> UTC.
>>
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>>
>> Here is my +1 : SUCCESS! [1:07:19.906103]
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



should we clean up dev-docs?

2021-10-15 Thread Michael Sokolov
I was poking around looking for info on how we release Lucene, and I
stumbled into this dev-docs folder. It seems to have info that's
mostly useful for solr workflows, assumes you are working in
lucene-solr repo, etc. The info about pmc-chair seems helpful, and
maybe Putnam's guide to using git worktree, which was new to me, but
the rest should probably go / get updated to refer to lucene repo.

One question I have is about this adoc format - is it processed by
something and published somewhere, or is this just intended to be read
in the source tree (or maybe on github). If it's the latter, maybe we
should switch to markdown?

Also, I did find the dev-tools folder and the release wizard. The
README.md in there is very helpful. I wonder if we ought to simply
consolidate the docs in dev-docs in here so they are easier to
discover together?

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



Re: Lucene 9.0 release

2021-10-15 Thread David Smiley
+1 Adrien.  Thanks for moving things along.

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Fri, Oct 15, 2021 at 3:30 AM Adrien Grand  wrote:

> For visibility, I recently opened a new issue about a case of index
> corruption  which is
> a blocker for 9.0. Nhat is looking into it.
>
> We've been discussing releasing 9.0 for a long time now and I think that
> everybody agrees with moving forward, there's even some good momentum
> around making the build and release tooling ready. So I'd like to propose
> the following timeline for the 9.0 release to get some feedback:
>
> 2021-11-01: Feature freeze:
>  - branch_9x gets created from main
>  - branch_8_11 gets created from branch_8x
> This gives us ~2 weeks to do some last-minute work. The reasoning for
> doing 8.11 as well is that we have some enhancements merged to branch_8x
> that I suspect some users would like to see released in 8.x. Important
> note: 8.11 will be the last minor release of major version 8. There might
> be new patch releases in the future such as 8.11.1 or 8.11.2, but there
> won't be a 8.12 or a 8.13.
>
> 2021-11-04: First RC for 8.11
> Since we had 8.10 not long ago, hopefully the release process will go
> smoothly.
>
> ~2021-11-10: First RC for 9.0
> The date is indicative, the plan would be to move forward with the first
> 9.0 RC as soon as the following conditions are met:
>  - 8.11 is out
>  - all 9.0 blockers have been addressed
>
> Mike, your previous email suggests that you would like someone else to
> step up. If that's correct I'm happy to be the release manager for both
> 8.11 and 9.0.
>
>
> On Sat, Oct 2, 2021 at 11:54 PM Michael Sokolov 
> wrote:
>
>> Yes! I'm curious to give it a go, but getting pulled in many different
>> directions. If nobody else steps up, I will be free to shepherd the
>> release along in a  couple of weeks, assuming the current firestorm
>> subsides...
>>
>> On Thu, Sep 30, 2021 at 9:54 AM Jan Høydahl 
>> wrote:
>> >
>> > +1
>> >
>> > Blockers seem to be done with. So I guess we just need an RM to get the
>> ball rolling? :)
>> >
>> > I know that the Release Wizard in new Lucene repo needs some updates
>> https://issues.apache.org/jira/browse/LUCENE-9809 - I may help some with
>> that...
>> >
>> > Cross-ref other 9.0 release mail-threads:
>> > - "Now that 8.10 is out ... let's get rolling on 9!"
>> https://lists.apache.org/thread.html/r868028d42a19ae02d5bbe2e3329da26869045002b9bb4760b8056c56%40%3Cdev.lucene.apache.org%3E
>> > - "9.0 release":
>> https://lists.apache.org/thread.html/r7bef0af668860fdbfedb4b58261efd01d9fb26dc280915284c121065%40%3Cdev.lucene.apache.org%3E
>> >
>> > Jan
>> >
>> > 17. aug. 2021 kl. 11:13 skrev Adrien Grand :
>> >
>> > +1 to your suggestions
>> >
>> > I just commented on LUCENE-9959 to suggest reverting since the changes
>> are currently half baked and I don't think that they should block 9.0.
>> There are no other blockers left to my knowledge.
>> >
>> > On Sat, Aug 14, 2021 at 6:24 PM Michael Sokolov 
>> wrote:
>> >>
>> >> It's been two years since our last release, we had lots of +1 when we
>> >> raised this last December, and IMO we are close to baked at this
>> >> point.
>> >>
>> >> I checked JIRA and found two remaining Blockers
>> >>
>> >> 1. https://issues.apache.org/jira/browse/LUCENE-10016
>> >> VectorReader.search needs rethought, o.a.l.search integration?
>> >> 2. https://issues.apache.org/jira/browse/LUCENE-8638 Remove deprecated
>> >> code in main
>> >>
>> >> The first one is very close to resolved;
>> >>
>> >> On the deprecations, the issue has lingered for 1-1/2 years now, and
>> >> some progress has been made, but more work remains. Some new
>> >> deprecations have been added since it was opened too. Maybe we make a
>> >> concerted effort to clean out as much as we can, and then decide if
>> >> it's enough? Anyway this seems to be the only outstanding issue, so
>> >> let's see if we can make progress there
>> >>
>> >> Q: any other blockers?
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> >> For additional commands, e-mail: dev-h...@lucene.apache.org
>> >>
>> >
>> >
>> > --
>> > Adrien
>> >
>> >
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>
>
> --
> Adrien
>


Re: Accessibility of CollectedSearchGroup's state

2021-10-15 Thread Chris Hegarty
Hi Adrien, Jim,

First, thank you for your time and insightful comments. They are very much 
appreciated, and will no doubt lead to the best solution.

I will reimplement the elasticsearch collector as suggested, and then circle 
back here with a proposal for the reduction in accessibility most appropriate 
for Lucene.

-Chris.

P.S. Eliminating split packages shines a spotlight on tech debt. Each case 
different and requiring / deserving of its own investigation and analysis. I 
try to do as much of this upfront, but really it needs the valuable input from 
folk on this list. Thank you for your time.

> On 14 Oct 2021, at 19:05, jim ferenczi  wrote:
> 
> I agree, we should have a SinglePassGroupingCollector in Elasticsearch and 
> reduce the visibility of these expert classes in Lucene.
> As it stands today, the FirstPassGroupingCollector could be a final class imo.
> 
> 
> Le jeu. 14 oct. 2021 à 18:42, Adrien Grand  > a écrit :
> I feel sorry for increasing the scope of all these requests for changes that 
> you make, but the way Elasticsearch overrides this collector feels wrong to 
> me as any change in the implementation details of this collector would 
> probably break Elasticsearch's collector too. In my opinion, 
> CollectedSearchGroup should not even be public. My preference would be to 
> copy this collector to the Elasticsearch code base and fold the changes from 
> Elasticsearch's CollapsingTopDocsCollector into it. I'm not super familiar 
> with this code, so I might be missing something. Maybe Jim or Alan have an 
> opinion.



Re: Lucene 9.0 release

2021-10-15 Thread Adrien Grand
For visibility, I recently opened a new issue about a case of index
corruption  which is a
blocker for 9.0. Nhat is looking into it.

We've been discussing releasing 9.0 for a long time now and I think that
everybody agrees with moving forward, there's even some good momentum
around making the build and release tooling ready. So I'd like to propose
the following timeline for the 9.0 release to get some feedback:

2021-11-01: Feature freeze:
 - branch_9x gets created from main
 - branch_8_11 gets created from branch_8x
This gives us ~2 weeks to do some last-minute work. The reasoning for doing
8.11 as well is that we have some enhancements merged to branch_8x that I
suspect some users would like to see released in 8.x. Important note: 8.11
will be the last minor release of major version 8. There might be new patch
releases in the future such as 8.11.1 or 8.11.2, but there won't be a 8.12
or a 8.13.

2021-11-04: First RC for 8.11
Since we had 8.10 not long ago, hopefully the release process will go
smoothly.

~2021-11-10: First RC for 9.0
The date is indicative, the plan would be to move forward with the first
9.0 RC as soon as the following conditions are met:
 - 8.11 is out
 - all 9.0 blockers have been addressed

Mike, your previous email suggests that you would like someone else to step
up. If that's correct I'm happy to be the release manager for both 8.11 and
9.0.


On Sat, Oct 2, 2021 at 11:54 PM Michael Sokolov  wrote:

> Yes! I'm curious to give it a go, but getting pulled in many different
> directions. If nobody else steps up, I will be free to shepherd the
> release along in a  couple of weeks, assuming the current firestorm
> subsides...
>
> On Thu, Sep 30, 2021 at 9:54 AM Jan Høydahl  wrote:
> >
> > +1
> >
> > Blockers seem to be done with. So I guess we just need an RM to get the
> ball rolling? :)
> >
> > I know that the Release Wizard in new Lucene repo needs some updates
> https://issues.apache.org/jira/browse/LUCENE-9809 - I may help some with
> that...
> >
> > Cross-ref other 9.0 release mail-threads:
> > - "Now that 8.10 is out ... let's get rolling on 9!"
> https://lists.apache.org/thread.html/r868028d42a19ae02d5bbe2e3329da26869045002b9bb4760b8056c56%40%3Cdev.lucene.apache.org%3E
> > - "9.0 release":
> https://lists.apache.org/thread.html/r7bef0af668860fdbfedb4b58261efd01d9fb26dc280915284c121065%40%3Cdev.lucene.apache.org%3E
> >
> > Jan
> >
> > 17. aug. 2021 kl. 11:13 skrev Adrien Grand :
> >
> > +1 to your suggestions
> >
> > I just commented on LUCENE-9959 to suggest reverting since the changes
> are currently half baked and I don't think that they should block 9.0.
> There are no other blockers left to my knowledge.
> >
> > On Sat, Aug 14, 2021 at 6:24 PM Michael Sokolov 
> wrote:
> >>
> >> It's been two years since our last release, we had lots of +1 when we
> >> raised this last December, and IMO we are close to baked at this
> >> point.
> >>
> >> I checked JIRA and found two remaining Blockers
> >>
> >> 1. https://issues.apache.org/jira/browse/LUCENE-10016
> >> VectorReader.search needs rethought, o.a.l.search integration?
> >> 2. https://issues.apache.org/jira/browse/LUCENE-8638 Remove deprecated
> >> code in main
> >>
> >> The first one is very close to resolved;
> >>
> >> On the deprecations, the issue has lingered for 1-1/2 years now, and
> >> some progress has been made, but more work remains. Some new
> >> deprecations have been added since it was opened too. Maybe we make a
> >> concerted effort to clean out as much as we can, and then decide if
> >> it's enough? Anyway this seems to be the only outstanding issue, so
> >> let's see if we can make progress there
> >>
> >> Q: any other blockers?
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>
> >
> >
> > --
> > Adrien
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

-- 
Adrien