Re: Proposing a 10.3 release in September

It should all be in the releaseWizard.py. Its a very interactive script, so you shouldn't need much prior information going into it. I believe the script can export to markdown or something similar, but I would recommend just running the script itself. - Houston On Mon, Aug 11, 2025 at 10:40 AM

Re: Welcome Stefan Vodita to the Lucene PMC

Welcome Stefan! - Houston On Tue, May 6, 2025 at 11:54 AM Uwe Schindler wrote: > Welcome Stefan! > > Uwe > Am 06.05.2025 um 18:19 schrieb Robert Muir: > > Welcome Stefan! > > Thank you esp for the work with the fun stuff such as CI and actions! > Keeps the lights on. > > On Sun, May 4, 2025, 5:

Re: Policeman Jenkins => new hardware

That's awesome! The tests are running really well now. Thanks for all this (continued) work, it's really appreciated!! - Houston On Mon, Mar 24, 2025 at 5:29 AM Uwe Schindler wrote: > Hi a small update, > > the new virtualization works phantastic. Windows builds are a bit slower > than others,

Re: [VOTE] Release Lucene 9.12.0 RC2

SUCCESS! [0:56:04.683348] +1 (binding) - Houston On Thu, Sep 26, 2024 at 4:02 AM Uwe Schindler wrote: > The latest smoketester run with all JDKs including JDK 23 succeeded > after 3.5 hrs: > > https://jenkins.thetaphi.de/job/Lucene-Release-Tester/37/console > > Tested were: > Java 11 JAVA_HOME

Re: [VOTE] Release Lucene 9.12.0 RC1

Thanks so much for getting the back compat stuff started Chris, that's a lot of help. I'm comparing these to the commits I made for the 8.11.3 release, and there are some discrepancies. But we can take care of that on the PRs. - Houston On Wed, Sep 25, 2024 at 8:37 AM Chris Hegarty < christopher

Re: [RESULT] [VOTE] Release Lucene/Solr 8.11.4 RC1

7;s largest organizations. Other major features > include Kubernetes and docker integration, streaming, highlighting, > faceting, and spellchecking. > - > > It says that Solr supports multi-modal and vector search, but this release > news is for Solr 8.11.4, so should we remove them? >

Re: [VOTE] Release Lucene/Solr 8.11.4 RC1

It's been >72h since the vote was initiated and the result is: +1 5 (5 binding) 0 0 -1 0 This vote has PASSED On Tue, Sep 24, 2024 at 12:41 PM Jan Høydahl wrote: > +1 > > SUCCESS! [1:29:27.098734] (on fifth run or something) > > Jan > > 19. sep. 2024 k

[RESULT] [VOTE] Release Lucene/Solr 8.11.4 RC1

It's been >72h since the vote was initiated and the result is: +1 5 (5 binding) 0 0 -1 0 This vote has PASSED

Re: [VOTE] Release Lucene/Solr 8.11.4 RC1

Btw I am +1 (binding) too, I must have missed copying that part of the message. - Houston On Tue, Sep 24, 2024 at 10:01 AM Anshum Gupta wrote: > +1 (binding) > > SUCCESS! [1:01:01.305159] > > On Thu, Sep 19, 2024 at 11:51 AM Houston Putman > wrote: > >> Please vote

Re: [VOTE] Release Lucene 9.12.0 RC1

Thanks for the offer Chris, I'll definitely take you up on that! And hopefully its done in a day or two. - Houston On Mon, Sep 23, 2024 at 3:28 PM Chris Hegarty wrote: > Thanks Uwe, > > I reproduced this failure on main and branch_9_12. > > The following issue has been created to track this, >

[VOTE] Release Lucene/Solr 8.11.4 RC1

Please vote for release candidate 1 for Lucene/Solr 8.11.4 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.4-RC1-reve27f44e3d78dfcec230c97e0a1240e3751daeff9 You can run the smoke tester directly with this command: python3 -u dev-tools/scripts/

Bugfix release Lucene/Solr 8.11.4

NOTICE: I am now preparing for a bugfix release from branch branch_8_11 Please observe the normal rules for committing to this branch: * Before committing to the branch, reply to this thread and argue why the fix needs backporting and how long it will take. * All issues accepted for backportin

Re: [VOTE] Release Lucene 9.11.1 RC1

+1 SUCCESS! [0:37:06.564011] - Houston On Tue, Jun 25, 2024 at 1:27 PM Anshum Gupta wrote: > +1 > > SUCCESS! [0:44:08.897482] > > On Sun, Jun 23, 2024 at 10:29 PM Ignacio Vera wrote: > >> Please vote for release candidate 1 for Lucene 9.11.1 >> >> >> The artifacts can be downloaded from: >> >

Re: [VOTE] Release Lucene 9.11.0 RC1

+1 SUCCESS! [1:49:36.192513] - Houston Putman On Wed, Jun 5, 2024 at 12:58 PM Michael McCandless < luc...@mikemccandless.com> wrote: > +1 SUCCESS! [0:24:55.332837] > > Mike McCandless > > http://blog.mikemccandless.com > > > On Wed, Jun 5, 2024 at 11:21 AM Adrien

Re: [Vote] Bump the Lucene main branch to Java 21

+1 - Houston On Mon, Feb 26, 2024 at 7:00 AM Jan Høydahl wrote: > +1 > > Jan > > 23. feb. 2024 kl. 20:01 skrev Patrick Zhai : > > +1 > > On Fri, Feb 23, 2024 at 9:34 AM Dawid Weiss wrote: > >> >> I'm fine with this requirement. >> >> +1. >> >> On Fri, Feb 23, 2024 at 12:24 PM Chris Hegarty >>

[ANNOUNCE] Apache Lucene 8.11.3 released

The Lucene PMC is pleased to announce the release of Apache Lucene 8.11.3. Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform. This

[RESULT] [VOTE] Release Lucene/Solr 8.11.3 RC1

It's been >72h since the vote was initiated and the result is: +1 6 (6 binding) 0 0 -1 0 This vote has PASSED

Re: [VOTE] Release Lucene/Solr 8.11.3 RC1

gt;> >>> SUCCESS! [1:18:24.494917] >>> >>> On Wed, 7 Feb 2024 at 18:24, Jan Høydahl wrote: >>> >>>> +1 (binding) >>>> >>>> SUCCESS! [1:18:11.930433] >>>> >>>> Only ran smoke tester. macOS, Temurin 1.8.0

[VOTE] Release Lucene/Solr 8.11.3 RC1

Please vote for release candidate 1 for Lucene/Solr 8.11.3 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.3-RC1-revbaa7c80af4278cc8951a344d8e9320386588d12d You can run the smoke tester directly with this command: python3 -u dev-tools/scripts/

Bugfix release Lucene/Solr 8.11.3

NOTICE: I am now preparing for a bugfix release from branch branch_8_11 Please observe the normal rules for committing to this branch: * Before committing to the branch, reply to this thread and argue why the fix needs backporting and how long it will take. * All issues accepted for backportin

Re: github milestones vs. releases mystery

Making a release in github is quite easy. You can do it from the release git tag, so it's "retroactive". (we can do it for 9.7.0 right now) For the release wizard, the Solr Operator has a section to do this: https://github.com/apache/solr-operator/blob/main/hack/release/wizard/releaseWizard.yaml#L

Final CFP Reminder: Community Over Code

Hello everyone, Today is the last day that you can submit a presentation for Community Over Code (formerly known as ApacheCon). Submissions will be accepted until 23:59:59 GMT. https://communityovercode.org/call-for-presentations/ There is a Search track that is perfect for presentations concern

Re: JavaDoc generated with -noindex

Yeah my bad, didnt read which list it was. On Sun, Jul 9, 2023 at 10:19 AM Uwe Schindler wrote: > Isn't this about Lucene? So 9.8 is right version. > Am 07.07.2023 um 23:43 schrieb Houston Putman: > > Agreed, should be an easy change to include for 9.3. > > - Houston >

Re: JavaDoc generated with -noindex

Agreed, should be an easy change to include for 9.3. - Houston On Fri, Jul 7, 2023 at 5:42 PM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > +1 to include this in release. Thanks for noticing! > > On Sat, 8 Jul, 2023, 12:33 am Mike Drob, wrote: > >> Why is our javadoc currently gene

Re: [VOTE] Dimension Limit for KNN Vectors

+1 on the combination of #3 and #4. Also good things to make sure of Uwe, thanks for calling those out. (Especially about the limit only being used on write, not on read). - Houston On Tue, May 16, 2023 at 9:57 AM Uwe Schindler wrote: > I agree with Dawid, > > I am +1 for those two options in

Re: Running 10.0 build with a custom lucene 9.5

Gus, I haven't done this myself, but are you using the instructions provided in Solr's "gradle/lucene-dev/lucene-dev-repo-composite.gradle"? It looks like you need to specify the development lucene version differently than other dependencies... - Houston On Sat, May 13, 2023 at 10:14 AM Michael

Re: Lucene PMC Chair Greg Miller

Thanks Bruno, and good luck Greg! - Houston On Tue, Mar 7, 2023 at 3:29 PM Gus Heck wrote: > Congratulations Greg and thanks Bruno! > > On Tue, Mar 7, 2023 at 3:13 PM Tomás Fernández Löbbe < > tomasflo...@gmail.com> wrote: > >> Thanks Bruno! and Congratulations Greg! >> >> On Tue, Mar 7, 2023 a

Re: [VOTE] Release Lucene 9.4.1 RC1

SUCCESS! [0:47:29.586134] + 1 On Fri, Oct 21, 2022 at 10:33 AM Michael Sokolov wrote: > SUCCESS! [0:49:28.580122] > > +1 > > On Fri, Oct 21, 2022 at 5:57 AM Robert Muir wrote: > > > > I change my vote to +1 based on Julie's test. It fails for me with > > 9.4.0 and passes for me with 9.4.1 > >

Re: Label vs. Milestone for version management?

So the Solr Operator has been using Github Issues for a few releases now, and the Milestone feature has worked really well for a blockers list. I agree that it should not be the canonical list of things that were included in that release (although it will likely be very close), but it is very good

Re: Welcome Vigya Sharma as Lucene committer

Welcome Vigya! On Mon, Aug 1, 2022 at 11:38 AM Alan Woodward wrote: > Congratulations and welcome, Vigya! > > - Alan > > On 28 Jul 2022, at 20:44, Vigya Sharma wrote: > > Thanks everyone for the warm welcome. It is an honor to be invited as a > Lucene committer, and I look forward to contributi

Re: [DISCUSS] Read-only Jira after the GitHub issues migration?

I think missing a few updates would be preferable to having 10k messages. Just my opinion though. On Tue, Jul 19, 2022 at 10:11 AM Tomoko Uchida wrote: > > 1. Make Jira read only >> >> At the very last step, we'll add comments saying "This was moved GitHub >> " to each Jira issue. It has to be d

Re: A prototype migration tool Jira to GitHub

> > Is there anybody who kindly provides a github account to make sure that > "any notifications are never triggered" when executing migration? I > confirmed this with my account, just wanted to test it with other one or > two accounts. > I've subscribed to all notifications for that sandbox-lucen

Re: Deleting old RCs

Definitely clean them up. It should be a step in the release wizard when aborting the failed RC or promoting the successful RC. (This is in the python code, not the yaml file.) I know it is in Solr, but maybe that got broken in the lucene release wizard after the split. Given the lucene-solr artif

Re: [VOTE] Release Lucene/Solr 8.11.2 RC2

+1 (binding) SUCCESS! [1:10:19.762602] - Houston On Wed, Jun 15, 2022 at 10:04 PM Anshum Gupta wrote: > Thanks for reporting that, Tim. > > Seems like this one is known to fail. I tried reproducing this w/ same > seed as well as randomizing, but wasn't able to do that over 100 runs. > > > On W

Re: [VOTE] Release Lucene/Solr 8.11.2 RC1

+0 SUCCESS! [1:02:38.547629] I saw this in the example logs during the smoketester: > ps: Invalid process id: i��\r\001 > Waiting up to 180 seconds to see Solr running on port 8983 [/] > Started Solr server on port 8983 (pid=16758). Happy searching! > This seems related to SOLR-16191

Re: Welcome Chris Hegarty as Lucene committer

Congrats Chris! On Thu, Jun 2, 2022 at 4:07 PM Mikhail Khludnev wrote: > Welcome, Chirs! > > On Wed, Jun 1, 2022 at 10:29 AM Chris Hegarty > wrote: > >> Hi, >> >> I am both honoured and humbled to have been invited to become a >> committer. Thank you. >> >> I've been working on the development

Re: Welcome Lu Xugang as Lucene committer

Congrats Lu! On Thu, Jun 2, 2022 at 4:09 PM Mikhail Khludnev wrote: > Welcome, Lu. > > On Wed, Jun 1, 2022 at 12:59 PM 陆徐刚 wrote: > >> Thanks Adrien for the announcement and all for the welcome! It’s a great >> honor for me be a Lucene committer. >> >> I live in ShangHai, China and work at EOI

Re: Welcome Greg Miller to the Lucene PMC

Welcome Greg! On Tue, Jun 7, 2022 at 11:35 AM Gautam Worah wrote: > Congratulations Greg! > > On Tue, Jun 7, 2022 at 8:04 AM Patrick Zhai wrote: > >> Congrats Greg! >> >> Patrick >> >> On Tue, Jun 7, 2022, 07:53 Julie Tibshirani wrote: >> >>> Congratulations Greg!! >>> >>> On Tue, Jun 7, 2022

Re: [VOTE] Migration to GitHub issue from Jira (LUCENE-10557)

+1 Approve (PMC) Thanks so much for doing all of the work for this Tomoko! - Houston On Mon, May 30, 2022 at 5:38 PM David Smiley wrote: > +1 Approve (PMC) > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Mon, May 30, 2022 at 11:40 AM

Re: [VOTE] Release Lucene 9.2.0 RC2

+1 SUCCESS! [2:17:07.370407] (java 11 & 17) - Houston On Fri, May 20, 2022 at 8:04 AM Jan Høydahl wrote: > +1 > > SUCCESS! [1:13:38.226868] > > Jan > > > 19. mai 2022 kl. 17:16 skrev Alan Woodward : > > > > Please vote for release candidate 2 for Lucene 9.2.0 > > > > The artifacts can be downl

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

github.com/helm/helm > > On Tue, May 10, 2022 at 10:16 AM Gus Heck wrote: > >> >> >> On Tue, May 10, 2022 at 10:40 AM Houston Putman >> wrote: >> >>> >>>> >>> Most modern open source projects use Github Issues for their iss

Re: [DISCUSS] A proposal for migration to GitHub issue (LUCENE-10557)

> > It's not about features, but about accepting a new framework to me. GitHub > issue would not be a replacement Jira, and we cannot operate this project > on GitHub issue in the same way on Jira. We'd need to build our new > convention and operations on the new toolkit. > I think this is a very

Re: Lucene PMC Chair Bruno Roustant

Congrats Bruno, and thanks Michael for doing such an incredible job! - Houston On Thu, Mar 24, 2022 at 10:45 AM Alessandro Benedetti wrote: > Thanks Michael for the amazing work last year! > Welcome Bruno, I am sure you'll do great! > Cheers > > On Thu, 24 Mar 2022, 09:23 Uwe Schindler, wrote:

Re: Welcome Guo Feng as Lucene committer

Congrats Feng! On Fri, Jan 28, 2022 at 12:31 AM Michael Gibney wrote: > Welcome, Feng! > > On Thu, Jan 27, 2022 at 2:23 PM Mayya Sharipova > wrote: > >> Welcome and congratulations, Feng! >> >> On Wed, Jan 26, 2022 at 11:50 AM Namgyu Kim wrote: >> >>> Congratulations and welcome, Feng! :D >>>

Re: Mirroring the later 8.x release tags in the "new" split repositories

them. Since these projects > > share a common root, there is nothing to prevent this from happening. > > Then tags point at actual revisions and everything makes sense. > > > > This does not change the fact that I don't really see much value in > > doing all this.

Re: Mirroring the later 8.x release tags in the "new" split repositories

They don't have those commits, but they also don't have the commits for the previous release tags in the repo. You can go to any of the release tags, choose a commit to view and you will get a message saying: > This commit does not belong to any branch on this repository, > and may belong to a fo

Mirroring the later 8.x release tags in the "new" split repositories

Hello all, As mentioned in SOLR-15874 , we are not hosting the tags for the latest 8.x releases in the split apache/solr and apache/lucene repositories. All release tags made prior to the repository split exist in the new repos, so I see no reason

Re: Welcome Haoyu (Patrick) Zhai as Lucene Committer

Congrats Haoyu! On Mon, Dec 20, 2021 at 12:42 PM Anshum Gupta wrote: > Congratulations and welcome, Haoyu! > > On Sun, Dec 19, 2021 at 1:12 AM Dawid Weiss wrote: > >> Hello everyone! >> >> Please welcome Haoyu Zhai as the latest Lucene committer. You may also >> know Haoyu as Patrick - this is

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

SUCCESS! [1:10:32.826846] Also ran Jan's docker image using the Solr Operator and everything looked good to me. I also tested some of the fixes included in the release. +1 (binding) - Houston On Wed, Dec 15, 2021 at 3:42 PM Timothy Potter wrote: > Awesome, thanks Uwe! > > On Wed, Dec 15, 2021

Re: Welcome Julie Tibshirani to the Lucene PMC

Congrats Julie, welcome! On Wed, Dec 1, 2021 at 9:27 PM Nhat Nguyen wrote: > Congratulations, Julie! > > On Wed, Dec 1, 2021 at 1:17 PM Julie Tibshirani > wrote: > >> Thank you everyone. I'm really looking forward to contributing! >> >> Julie >> >> On Wed, Dec 1, 2021 at 9:39 AM Michael Wechner

Re: [VOTE] Release Lucene/Solr 8.11.0 RC1

+1 SUCCESS! [1:04:19.544964] Also tested extensively with the Solr Operator. On Thu, Nov 11, 2021 at 1:06 PM Bruno Roustant wrote: > +1 > SUCCESS! [1:17:35.209577] > > Le jeu. 11 nov. 2021 à 18:30, Julie Tibshirani a > écrit : > >> +1 (nonbinding) >> SUCCESS! [1:04:58.967300] >> >> On Thu, Nov

Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

+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 < >> luc...@mikemccandless.c

Re: Bugfix release Lucene/Solr 8.10.1

Hey Mayya, I think there are some issues with the lucene changelog entries in 8.10.1 across various branches (branch_8_10, branch_8x, and main). I don't see LUCENE-10119, and LUCENE-10126 is marked as an 8.11.0 entry in at least branch_8x. - Houston On Thu, Oct 7, 2021 at 9:32 PM Mayya Sharipova

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

SUCCESS! [1:04:04.335749] I also ran through some manual testing with the new s3-repository contrib using your convenience docker image, and it worked as expected. +1 On Fri, Sep 24, 2021 at 4:37 AM Namgyu Kim wrote: > +1 SUCCESS! [1:01:04.224368] > > On Thu, Sep 23, 2021 at 12:42 AM Timothy P

Re: [JENKINS-MAVEN] Lucene » Lucene-Solr-Maven-8.x #379: POMs out of sync

> No worries. Thanks for the confirmation! > > Cheers, > -Greg > > On Mon, Aug 23, 2021 at 12:21 PM Houston Putman > wrote: > > > > Yes it would. I forgot to remove the non-needed dependency from > everywhere it seems. I'll get it working soon. Sorry for the ann

Re: [JENKINS-MAVEN] Lucene » Lucene-Solr-Maven-8.x #379: POMs out of sync

gt; > 43229/home/runner/work/lucene-solr/lucene-solr/lucene/tools/custom-tasks.xml:108: > Lib versions check failed. Check the logs. > > Cheers, > -Greg > > > On Mon, Aug 23, 2021 at 9:37 AM Houston Putman > wrote: > > > > Thanks for calling this out Mike. >

Re: [JENKINS-MAVEN] Lucene » Lucene-Solr-Maven-8.x #379: POMs out of sync

Thanks for calling this out Mike. It's related to SOLR-15089 . I'll get it sorted out, as well as some test flakiness that were introduced by that ticket. - Houston On Mon, Aug 23, 2021 at 6:56 AM Michael McCandless < luc...@mikemccandless.com> w

Re: Welcome Mayya Sharipova to the Lucene PMC

Congrats and welcome Mayya! On Wed, Jun 30, 2021 at 3:17 PM Tim Allison wrote: > Welcome Mayya! > > On Wed, Jun 30, 2021 at 1:07 PM Christine Poerschke (BLOOMBERG/ > LONDON) wrote: > > > > Welcome Mayya! > > > > From: dev@lucene.apache.org At: 06/28/21 14:16:54 UTC+1:00 > > To: dev@lucene.apach

Re: Welcome Greg Miller as Lucene committer

Congrats and welcome Greg! On Tue, Jun 1, 2021 at 8:42 AM Gus Heck wrote: > Welcome Greg :) > > On Tue, Jun 1, 2021 at 12:03 AM Tomás Fernández Löbbe < > tomasflo...@gmail.com> wrote: > >> Congrats Greg!! >> >> On Mon, May 31, 2021 at 9:37 AM Gautam Worah >> wrote: >> >>> Congratulations Greg :

Re: Release Lucene/Solr 8.9.0 should we have it soon

Mayya, SOLR-14978 is now in 8.x. So no longer a blocker. - Houston On Thu, May 27, 2021 at 11:42 PM David Smiley wrote: > SOLR-15412 is rather serious as the title suggests. I haven't been > tracking the progress so if it's already resolved, that's unknown to me and > isn't reflected in JIRA.

Re: Release Lucene/Solr 8.9.0 should we have it soon

Hey Mayya, would you mind to wait until at least Tuesday (6/1)? We are trying to backport SOLR-14978 to 8.x, and would really like it included in 8.9. - Houston On Thu, May 27, 2021 at 5:24 PM Mayya Sharipova wrote: > Hello everyone, > I wonder if everyone is ok for May 31st (Monday) as the da

Re: Separate git repo(s) for Solr modules

gt; From the Solr perspective, Lucene and Zookerper are really two “similar” > dependencies and IMO we should think about them in that way. > > Ilan > > On Tue 4 May 2021 at 09:45, Noble Paul wrote: > >> @Houston >> >> So, Are you suggesting we should not do that ?

Re: Separate git repo(s) for Solr modules

In the future we wont be able to “work on both at the same time”, once Lucene 9 is cut. Why not pull that bandaid now? On Mon, May 3, 2021 at 11:32 PM Noble Paul wrote: > I'm still struggling to understand the workflow when I'm working on a > feature that spans lucene and solr. > > I'm yet to se

Re: Welcome Peter Gromov as Lucene committer

Congrats! On Wed, Apr 7, 2021 at 12:47 PM Anshum Gupta wrote: > Congratulations and welcome, Peter! > > On Tue, Apr 6, 2021 at 10:48 AM Robert Muir wrote: > >> I'm pleased to announce that Peter Gromov has accepted the PMC's >> invitation to become a committer. >> >> Peter, the tradition is tha

Re: Request times metric for collection

Hey Alex, This is likely a better question for us...@solr.apache.org. - Houston On Tue, Mar 16, 2021 at 12:39 AM Alex Bulygin wrote: > Good afternoon everyone! Someone can tell me please, metric request time > can be taken only by cores? Are there any aggregates on the collection or > in the c

Re: [solr-operator] branch main updated (fc76f66 -> 75830c3)

Should be done now. https://github.com/apache/solr-operator/commit/d236b4f2cc2713c410554cc5166064b566b58342#diff-b4c2a69650f9ac84008ad9f745859a645c9466350ffdfe5f919655039ee2e2c3 - Houston On Mon, Mar 15, 2021 at 1:37 PM Uwe Schindler wrote: > Hi Houston, > > Can we change the commit mail addre

Re: Welcome Bruno to the Apache Lucene PMC

Congrats and welcome Bruno! On Thu, Mar 11, 2021 at 8:32 AM David Smiley wrote: > Welcome Bruno! > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Wed, Mar 10, 2021 at 7:56 PM Mike Drob wrote: > >> I am pleased to announce that Bruno has

Re: Separate Solr build: help with the remaining last mile needed.

For posterity, the docker build broke because github changed the version of ubuntu_latest in github actions from 18.04 to 20.04. The ACL package is installed by default in Ubuntu 18, but not Ubuntu 20. Installing it at the beginning of the docker action fixes the build. On Fri, Mar 5, 2021 at 3:2

Re: Separate Solr build: help with the remaining last mile needed.

cal build. > > D. > > On Thu, Mar 4, 2021 at 7:45 PM Houston Putman > wrote: > > > > It worked as of 10 days ago: > https://github.com/apache/lucene-solr/actions/workflows/docker-test.yml > > > > I created a test PR to see if it works based on master: > https:

Re: Separate Solr build: help with the remaining last mile needed.

on the branch only (does it work on > master)? > > Dawid > > On Thu, Mar 4, 2021 at 6:48 PM Houston Putman > wrote: > > > > I'm not sure why the docker github action is failing... I've tried it > locally and it works fine. I'll do some more investig

Re: Separate Solr build: help with the remaining last mile needed.

I'm not sure why the docker github action is failing... I've tried it locally and it works fine. I'll do some more investigation. On Thu, Mar 4, 2021 at 3:25 AM Dawid Weiss wrote: > Hi folks, > > I'll need some help with some remaining tasks to make the transition > easier after the solr repo sp

Re: Proposal for the Lucene Dependency after git repo split

o depend on Lucene snapshots >>> because that constrains the ability to do releases. Either you have to wait >>> for a Lucene release and then you can cut over, or you have to figure out >>> what changes you need to roll back. >>> >>> Features today rare

Re: Proposal for the Lucene Dependency after git repo split

epo controlled by the ASF that could be used? (An implementation of Apache > Archiva?) This would have the added benefit of allowing solr to detect when > Lucene breaks something before its released. > > On Thu, Feb 25, 2021 at 4:50 PM Houston Putman > wrote: > >> Hey everyone,

Proposal for the Lucene Dependency after git repo split

Hey everyone, Currently there is discussion going on, in SOLR-14762 , regarding the split of the lucene-solr repo into individual repos for Solr and Lucene. There seems to be agreement that we shouldn't wait for a Lucene release to do the split, an

Re: Solr Docker Dependencies Question

dirmngr: We used to use gpg for validating the downloaded solr binaries. That is gone in the new build (though will have to be added back in depending on what we decide around the "official image"). It can be removed for now and added back later if needed. Netcat: I believe netcat is for easy test

Re: Congratulations to the new Lucene PMC Chair, Michael Sokolov!

Congrats Michael! On Thu, Feb 18, 2021 at 11:52 AM Martin Gainty wrote: > поздравления! > > > -- > *From:* Julie Tibshirani > *Sent:* Wednesday, February 17, 2021 9:13 PM > *To:* Lucene Dev > *Subject:* Re: Congratulations to the new Lucene PMC Chair, Michael > Soko

Re: Congratulations to the new Apache Solr PMC Chair, Jan Høydahl!

Congrats Jan!! On Thu, Feb 18, 2021 at 2:21 PM Tomás Fernández Löbbe wrote: > Congratulations Jan! > > On Thu, Feb 18, 2021 at 10:56 AM Anshum Gupta > wrote: > >> Hi everyone, >> >> I’d like to inform everyone that the newly formed Apache Solr PMC >> nominated and elected Jan Høydahl for the po

Re: [VOTE] Release Lucene/Solr 8.8.1 RC2

SUCCESS! [1:01:43.630010] +1 (binding) On Wed, Feb 17, 2021 at 3:05 PM Tomás Fernández Löbbe wrote: > SUCCESS! [1:07:31.079810] > > Tested upgrading from 8.7 and saw no problems > > +1 (binding) > > On Wed, Feb 17, 2021 at 2:58 AM Noble Paul wrote: > >> SUCCESS! [1:04:46.520370] >> >> +1 Bindi

Re: package-tgz-src / package-src-tgz equivilent missing from gradle build on master?

Thanks for getting the list of steps currently taken. These are easy to keep in the gradle task: - excluding jdk javadoc package-list files (for licensing reasons evidently) - setting chmod bits on scripts building Changes.html from CHANGES.txt > I'm not sure building Changes.html is a

Re: Solr Docker discussion

Thanks for your input Hoss and Martijn. So I've taken a look at the Elastic docker images [1], and they are structured much like official images, except for the use of multi-stage builds. They have no ARGs, and the docker context is merely the directory in which the Dockerfile sits. With this in m

Re: g...@apache.org and lucene-solr-operator

There was an unfortunate period where the repo was migrated, but we weren't able to make the necessary changes to the mailing lists. They should have been fixed roughly a week ago though. The new GH Issue/PR emails should be going to the "issues" list. - Houston On Thu, Jan 21, 2021 at 4:12 PM D

Re: [VOTE] Release Lucene/Solr 8.8.0 RC1

+1 SUCCESS! [1:01:28.552891] On Tue, Jan 19, 2021 at 1:53 PM Cassandra Targett wrote: > I’ve put up the DRAFT version of the Ref Guide for 8.8: > https://lucene.apache.org/solr/guide/8_8/. > > I also created the Jenkins job for building the 8.8 guide which pushes to > the Nightlies server in ca

Re: Solr Docker discussion

l work when updating the base image for a >> released image? The image for a tag should be immutable (IMHO), and I think >> people would be surprised if 8.8.0 suddenly changed even if it was for a >> good reason such as fixing a CVE in the base image. But based on what Kevin >

Re: Solr Docker discussion

build and test locally with a Docker image > that matches what an "official" Docker image is. This should still be a > goal, but we should be able to rebuild the Solr docker image without > rebuilding all of Solr. > > PS - I chatted a bit with Houston on Slack about this to

Solr Docker discussion

There's a few decisions that need to be ironed out around the Solr docker image before 9.0 is released. This is because the community has decided that Solr should start releasing it's own docker images starting with 9.0. Below is the current state of the ongoing discussions for the Solr Docker ima

Re: Separate git repo(s) for Solr modules

I think it is a good idea to have solr-extras and solr-sandbox. However, I think it's fine if some projects in solr-extras need to be migrated into their own repos at some point. I don't necessarily agree with moving all contrib modules out of the main repo however. I think it makes the most sense

Re: Failing gradle precommits

-x test" to "gradlew precomit" > ? CC Michael Sokolov > >> > >> ~ David Smiley > >> Apache Lucene/Solr Search Developer > >> http://www.linkedin.com/in/davidwsmiley > >> > >> > >> On Fri, Jan 8, 2021 at 1:06 PM Timothy

Re: Failing gradle precommits

Weirdly enough, Github PR precommit actions have started to OOM. Not sure if it's a github thing or something that changed on our end... On Fri, Jan 8, 2021 at 11:37 AM Joel Bernstein wrote: > It turned out to be this while I merged branches: > > warning: inexact rename detection was skipped due

Re: 2021-01 Lucene/Solr Committer meeting

I agree with Mike, the ref-branch is a topic that will take much more than an hour. I don't think the idea is to limit discussion around the ref-branch, but instead to separate it out so that other topics are given the time that they need. - Houston On Thu, Jan 7, 2021 at 2:08 PM Ishan Chattopadh

Re: Guohua Wu's subscription to lucene dev list

Hello, You can find instructions here on how to subscribe to the lucene mailing lists. (You send an email to dev-subscribe) https://lucene.apache.org/core/discussion.html#developer-lists - Houston On Thu, Jan 7, 2021 at 10:02 AM guohuawu227 wrote: > I am a software developer from China.My nam

Re: 8.8 Release

Thanks for volunteering Ishan. I think it might be a good idea to wait to cut and release 8.8 at least a week into January. Many people are going to be away during the holiday season, and particularly the last week of the year. Pushing into January just gives more people a chance to look at the re

Re: Welcome Houston Putman to the PMC

>> ~ David Smiley >> Apache Lucene/Solr Search Developer >> http://www.linkedin.com/in/davidwsmiley >> >> >> On Tue, Dec 1, 2020 at 4:20 PM Mike Drob wrote: >> >>> I am pleased to announce that Houston Putman has ac

Re: Solr: Separate CHANGES.txt for Docker, SolrJ, Contribs, ...

+1 I think that having separate CHANGES.txt files for the different parts of Solr would be great. If you are looking for certain changes you would generally know which module to go to. Some items that have a more sweeping impact would be listed in both I am ambivalent on having a separate CHANG

Re: Welcome Julie Tibshirani as Lucene/Solr committer

Congrats and welcome Julie!! - Houston On Wed, Nov 18, 2020 at 10:30 AM Eric Pugh wrote: > I’ve seen all your contributions, really great stuff. Welcome! > > > On Nov 18, 2020, at 10:22 AM, Uwe Schindler wrote: > > Welcome Julie! > > - > Uwe Schindler > Achterdiek 19, D-28357 Bremen > http

Re: [VOTE] Release Lucene/Solr 8.7.0 RC1

+1 (non-binding) SUCCESS! [1:02:05.573929] On Fri, Oct 30, 2020 at 4:56 PM Tomás Fernández Löbbe wrote: > +1 > > SUCCESS! [1:03:01.296851] > > On Fri, Oct 30, 2020 at 12:05 PM Nhat Nguyen > wrote: > >> +1 (binding) >> SUCCESS! [0:53:20.894728] >> >> >> On Fri, Oct 30, 2020 at 1:50 PM Michael M

Re: [DISCUSS] Solr Operator grant to Apache Lucene

I can answer a few of those! I assume this is a donation to Solr project, so it will be an > apache/solr-operator project, similar to how it is currently > lucene-solr? > Yes, the target would be apache/solr-operator. Similar to apache/rocketmq-operator

Re: 8.7 Release

gt;>>>>>> [exec] Crawl/parse... >> >> >>>>>>> [exec] >> >> >>>>>>> [exec] Verify... >> >> >>>>>>> [echo] Checking for malformed docs... >> >> >>>>>>

Re: JIRAs with user facing changes

I think this is a really good idea. Formalizing the process would certainly help with consistency throughout Solr. Thanks for bringing it up Noble! Andrzej, we could possibly use a label for this in JIRA, or add a "component" for it. Adding it as a part of the checklist is a good idea, especially

Re: 8.7 Release

Adrien, I plan on merging SOLR-14907 to master and 8x tomorrow. If you would mind waiting to cut 8.7 until then, I would appreciate it. - Houston On Mon, Oct 12, 2020 at 4:59 AM Adrien Grand wrote: > Shall we move forward with 8.7 now that 8.6.

Re: 8.6.3 Release

) > > Additionally, should we also consider a Jetty upgrade for 8.6.3 in > light of the issue mentioned above? I know it's atypical for bug-fix > releases to change deps, but here the bug is serious and tied directly > to the dep. SOLR-14897 and SOLR-14898 help greatly here, but t

  1   2   3   >