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

+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 >> wrote: >>> Hi, >>> >>> Since the

Re: [VOTE] Release Lucene 9.10.0 RC1

+1 (binding) SUCCESS! [0:50:52.035790] Jan > 14. feb. 2024 kl. 20:28 skrev Adrien Grand : > > Please vote for release candidate 1 for Lucene 9.10.0 > > The artifacts can be downloaded from: >

Re: [VOTE] Release Lucene/Solr 8.11.3 RC1

+1 (binding) SUCCESS! [1:18:11.930433] Only ran smoke tester. macOS, Temurin 1.8.0_402 Jan > 5. feb. 2024 kl. 23:23 skrev Houston Putman : > > Please vote for release candidate 1 for Lucene/Solr 8.11.3 > > The artifacts can be downloaded from: >

Re: [VOTE] Release Lucene 9.9.2 RC1

+1 Only ran smoke tester SUCCESS! [0:55:39.348431] Jan > 25. jan. 2024 kl. 12:57 skrev Chris Hegarty > : > > Please vote for release candidate 1 for Lucene 9.9.2 > > The artifacts can be downloaded from: >

Re: [VOTE] Release Lucene 9.9.1 RC1

+1 (binding, smoketester only) SUCCESS! [1:03:56.025355] Jan > 13. des. 2023 kl. 12:55 skrev Chris Hegarty > : > > Hi, > > Please vote for release candidate 1 for Lucene 9.9.1 > > The artifacts can be downloaded from: >

Re: Lucene 9.9.0 Release

+1 to a 9.9.0 release, thanks for volunteering. And also positive to immediately start planning the 10.0 release. JDK bump -> 17 is a major "feature" in itself, so we can bump main branch to 21 too. And discontinue support for 8.x after the 8.11.3 release. Jan > 22. nov. 2023 kl. 17:11 skrev

Re: Bump minimum Java version requirement to 21

+1 to a 10.0 on JDK17. There is no "agreement" anywhere to follow a 2-year cadence for major versions, even if that's been a pattern. Adopting a new JDK with clear benefits or getting off an EOL JDK should be valid arguments for considering a new major. If downstream wants to keep supporting

Re: [VOTE] Release Lucene/Solr 8.11.3 RC1

Hi, Thanks for doing the release. I'm running smoke tester However, there seems to be still open blocker issues in JIRA: https://issues.apache.org/jira/issues/?filter=12352945 I just resolved one other that was solved yesterday, but for the remaining three I cannot see that they are fixed. Not

Re: 8.11.3 release

, Ishan Chattopadhyaya < >>>>> ichattopadhy...@gmail.com> wrote: >>>>> >>>>>> Just a reminder to backport any issues one sees fit for a 8.11.3 >>>> release. >>>>>> I'll try to get an RC out by the end of September, so sti

Re: [VOTE] Release Lucene 9.8.0 RC1

Smoke tester only SUCCESS! [1:22:37.441415] +1 (binding) Jan > 22. sep. 2023 kl. 07:48 skrev Patrick Zhai : > > Please vote for release candidate 1 for Lucene 9.8.0 > > The artifacts can be downloaded from: >

Re: 8.11.3 release

Hi, Following up on Ishan's proposed 8.11.3 release (https://lists.apache.org/thread/3xjtv1sxqx8f9nvhkc0cb90b2p76nfx2) Does the Lucene project have any bugfix candidates for backporting? Ishan, are you still targeting September? Jan > 1. aug. 2023 kl. 14:57 skrev Ishan Chattopadhyaya : >

Re: Lucene PMC Chair Greg Miller

Thank you Bruno and Greg! Jan > 6. mar. 2023 kl. 18:15 skrev Bruno Roustant : > > Hello Lucene developers, > > Lucene Program Management Committee has elected a new chair, Greg Miller, and > the Board has approved. > > Greg, thank you for stepping up, and congratulations! > > > - Bruno

Re: Release wizard: generage asciidoc guide

Hi, It is just a convenience for generating a "print" version of the entire release process. It will generate an .adoc file and if you have asciidoctor installed you will also get it converted to HTML. Jan > 31. jan. 2023 kl. 10:58 skrev Luca Cavanna : > > Hi all, > I was wondering what the

Re: [VOTE] Release Lucene 9.5.0 RC1

+1 SUCCESS! [0:36:32.191785] Jan > 25. jan. 2023 kl. 19:43 skrev Luca Cavanna : > > Please vote for release candidate 1 for Lucene 9.5.0 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.5.0-RC1-rev-13803aa6ea7fee91f798cfeded4296182ac43a21 > >

Re: [lucene] branch main updated: Prevent NPEs while still handling the polar case for horizontal planes right off the pole

I’m not on Windows myself, but I think the trick is doing the git clone to the WSL file system. So you may have one checkout for use with windows and another for use within wsl. And if you’re a CLI person, there’s a GitHub cli tool ‘hub’ that is handy: https://hub.github.com/ Jan Høydahl

Re: [JENKINS] Lucene » Lucene-Check-9.4 - Build # 509 - Failure!

That's a good question. The wizard already has a mapping from Solr version to Java version and a method to find correct java_home and java_cmd: https://github.com/dweiss/lucene/blob/main/dev-tools/scripts/releaseWizard.py#L590:L600 So perhaps we need some logic to set correct JAVA_HOME and path

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

You'll not be able to create a GH issue with a script, on behalf of the original reporter. Neither will you be able to add a GH issue comment impersonating the person who made the JIRA comment. Rather, all issues and all comments would be made by the script/bot user, and you'd have to add in

Re: Deleting old RCs

I think I saw the same during Solr 9 release, it was fixed in https://github.com/apache/solr/commit/d51355256e4adc4ff1a03022e61ae1911601ccb7 and may need backport. There are also other fixes in Solr wizard that can

Re: [RESULT] [VOTE] Migration to GitHub issue from Jira

+1 for a manual approach Over time the volume will gravitate to mostly GitHub issues. And JIRA will always remain as an archive, so nothing is lost. Devs can always peek into the list of open JIRAs any time and choose to start a PR for one. A slight disadvantage is of course that in the first

Re: [VOTE] Release Lucene/Solr 8.11.2 RC2

+1 (binding) SUCCESS! [1:19:45.192785] Jan > 13. jun. 2022 kl. 21:05 skrev Mike Drob : > > Please vote for release candidate 2 for Lucene/Solr 8.11.2 > > The artifacts can be downloaded from: >

Re: Welcome Greg Miller to the Lucene PMC

Welcome Greg! Jan > 7. jun. 2022 kl. 08:36 skrev Adrien Grand : > > I'm pleased to announce that Greg Miller has accepted an invitation to join > the Lucene PMC! > > Congratulations Greg, and welcome aboard! > > -- > Adrien

Re: Welcome Lu Xugang as Lucene committer

Welcome and congratulations! Jan > 1. jun. 2022 kl. 09:07 skrev Adrien Grand : > > I'm pleased to announce that Lu Xugang has accepted the PMC's > invitation to become a committer. > > Xugang, the tradition is that new committers introduce themselves with a > brief bio. > > Congratulations

Re: Welcome Chris Hegarty as Lucene committer

Welcome Chris! Jan > 1. jun. 2022 kl. 09:04 skrev Adrien Grand : > > I'm pleased to announce that Chris Hegarty has accepted the PMC's > invitation to become a committer. > > Chris, the tradition is that new committers introduce themselves with a > brief bio. > > Congratulations and welcome!

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

+1 Approve (PMC) I'm not worried about reliance on GitHub as it is already approved by ASF. This will lower the barrier to participation for new contributors. - Jan > 30. mai 2022 kl. 17:39 skrev Tomoko Uchida : > > Hi everyone! > > As we had previous discussion thread [1], I propose

Re: Bugfix release Lucene/Solr 8.11.2

I bumped Jackson in https://issues.apache.org/jira/browse/SOLR-16213 <https://issues.apache.org/jira/browse/SOLR-16213> and also backported to 8_11. Wdyt? Jan > 18. mai 2022 kl. 15:22 skrev Gus Heck : > > SOLR-16194 is in and ported to 8.11,.2 > > On Wed, May 18, 2022 a

Re: [VOTE] Release Lucene 9.2.0 RC2

+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 downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.2.0-RC2-rev-ba8c3a806ada3d7b3c34d408e449a92376a8481b > >

Re: Bugfix release Lucene/Solr 8.11.2

I was pinged on https://issues.apache.org/jira/browse/SOLR-16019 because I have an in-flight PR with a backport. I'll complete and merge that PR. Jan > 13. mai 2022 kl. 01:03 skrev Mike Drob : > > To: dev@lucene, dev@solr > > NOTICE: > > I

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

For code changes, patch files in Jira used to be the only option. Over the years, this is almost completely replaced by PRs, but we still leave the door open for patch in JIRA. We could apply the same principle here: Don't shut down JIRA, but change documentation so that GitHub issues is

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

ASF has officially blessed use of github issues as alternative to Jira. They are not going to setup a private GitLab or tool X. While GitLab is nice, I don't think the main intention with the proposal was to inroduce yet another platform where contributors need to register an account and learn

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

Given how JIRA has become a monster of a product with different markup syntax for each version, and bugs everywhere (does not even work on mobile), I'm no longer the JIRA fan I once was. In Solr we already use github issues for the Solr-Operator sub project

Re: Release notes draft for Apache Solr 9.0

Thanks Anshum, I'm moving this mail thread from the Lucene dev-list to the Solr dev-list :) I think, as this is a major release, we should say explicitly in the release-notes something like: "This is a major-version release with several features removed and other major, breaking changes.

Re: Lucene PMC Chair Bruno Roustant

Congrats Bruno, and thank you Michael for a steady hand on the tiller last term! Jan > 23. mar. 2022 kl. 14:02 skrev Michael Sokolov : > > Hello, Lucene developers. Lucene Program Management Committee has > elected a new chair, Bruno Roustant, and the Board has approved. > Bruno, thank you for

Re: [VOTE] Release Lucene 9.1.0 RC1

figured out how to do it. You can passe xtra args at end of smoke tester > command line. > > - > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de <https://www.thetaphi.de/> > eMail: u...@thetaphi.de <mailto:u...@thetaphi.de> > > From:

Re: [VOTE] Release Lucene 9.1.0 RC1

Click the "Advanced" button for the "Invoke Gradle script" task, and you get the chance to pass "Project properties" as well as "Switches" and "System properties". Jan > 15. mar. 2022 kl. 13:12 skrev Uwe Schindler : > > Hi, > > I have a problem with running Smoketester (like on every

Re: Welcome Guo Feng as Lucene committer

Welcome Feng! Jan > 25. jan. 2022 kl. 10:09 skrev Adrien Grand : > > I'm pleased to announce that Guo Feng has accepted the PMC's > invitation to become a committer. > > Feng, the tradition is that new committers introduce themselves with a > brief bio. > > Congratulations and welcome! > >

Re: Welcome Haoyu (Patrick) Zhai as Lucene Committer

Welcome Patrick! Jan > 19. des. 2021 kl. 10:11 skrev Dawid Weiss : > > Hello everyone! > > Please welcome Haoyu Zhai as the latest Lucene committer. You may also > know Haoyu as Patrick - this is perhaps his kind gesture to those of > us whose tongues are less flexible in pronouncing difficult

Re: Log4j < 2.15.0 may still be vulnerable even if -Dlog4j2.formatMsgNoLookups=true is set

We make edits to the log4j advisory almost daily, see https://github.com/apache/solr-site/commits/e10a6a9fe0eed8dcba3ad1a076c8208e014e76ff/content/solr/security/2021-12-10-cve-2021-44228.md I wonder if we should include a "Revision history" paragraph in the advisory for transparency? Jan > 15.

[ANNOUNCE] Apache Lucene 8.11.1 released

The Lucene PMC is pleased to announce the release of Apache Lucene 8.11.1. 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.

Re: [JENKINS] Lucene » Lucene-NightlyTests-9.0 - Build # 45 - Failure!

Yep, I think it is a bad java11 upgrade on the jenkins server. All builds have been failing for a long time Jan > 17. des. 2021 kl. 13:08 skrev Dawid Weiss : > > This looks like the binary of java is broken somehow. > > On Fri, Dec 17, 2021 at 1:00 PM Apache Jenkins Server > wrote: >> >>

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

and, uschindler, dsmiley, gus, houston, anshum, atri, dweiss > 16. des. 2021 kl. 08:58 skrev Jan Høydahl : > > Thanks all, I'll close the vote now and start publishing the release... > > If you're a PMC member who planned to vote, but have not yet done so, there > is still value in

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

pta.net>> wrote: > Fast-track please :) > > On Wed, Dec 15, 2021 at 4:19 PM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Given the votes so far (11 binding +1) I'm also positive to publish tomorrow, > and not wait for Friday. > The release voting rules are three

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

tion. > > On Thu, 16 Dec, 2021, 2:40 am Anshum Gupta, <mailto:ans...@anshumgupta.net>> wrote: > +1 (binding) > > Smoke tester is happy. > > SUCCESS! [1:03:13.162577] > > Also tested out a sample search/indexing app. > > On Tue, Dec 14, 2021 at 6:36 A

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

ndler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > >> -Original Message- >> From: Jan Høydahl >> Sent: Tuesday, December 14, 2021 3:36 PM >> To: Lucene Dev >> Subject: [VOTE] Release Lucene/Solr

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

gain) and the script passed. > > started up a solr server from the unpacked download and verified it against a > few log4j injections, server responded appropriately each time > > manually verified a few of the other bugs having been fixed going into 8.11.1 > > SUCCES

Re: [VOTE] Release Lucene/Solr 8.11.1 RC1

/confluence/display/LUCENE/ReleaseNote8_11_1 ? Feel free to edit! Jan > 14. des. 2021 kl. 15:35 skrev Jan Høydahl : > > Please vote for release candidate 1 for Lucene/Solr 8.11.1 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/luce

[VOTE] Release Lucene/Solr 8.11.1 RC1

Please vote for release candidate 1 for Lucene/Solr 8.11.1 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.11.1-RC1-rev0b002b11819df70783e83ef36b42ed1223c14b50 You can run the smoke tester directly (from a fresh branch_8_11 checkout), with this

Re: Lucene/Solr 8.11.1 release

14, 2021 8:57 AM >> To: Lucene Dev >> Subject: Re: Lucene/Solr 8.11.1 release >> >> Jan, if you remember the names of the tests that fail, can you >> annotate them with @BadApple so that they will not fail when building >> new RCs or future 8.11 patch releases? >&

Re: Lucene/Solr 8.11.1 release

well, should we pick that one up if >> your next attempt fails? >> >> https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0 >> <https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0> >> >> On Mon, Dec 13, 2021 at 5:58

Re: Lucene/Solr 8.11.1 release

ache.org/log4j/2.x/changes-report.html#a2.16.0 > <https://logging.apache.org/log4j/2.x/changes-report.html#a2.16.0> > > On Mon, Dec 13, 2021 at 5:58 PM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Currently running 4th attempt at making buildAndPushRelease.py happy.

Re: Lucene/Solr 8.11.1 release

davidwsmiley > <http://www.linkedin.com/in/davidwsmiley> > > On Mon, Dec 13, 2021 at 9:34 AM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Including Lucene dev as well. > > As I see no Lucene level bug fixes for 8.11.1, I have prepared an "empty"

Re: Lucene/Solr 8.11.1 release

ome https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote8_11_1 There are now 18 CHANGES entries for Solr: https://github.com/apache/lucene-solr/blob/branch_8_11/solr/CHANGES.txt Jan > 13. des. 2021 kl. 02:24 skrev Jan Høydahl : > > There seems to be no open blockers for 8.11

Re: Closing GitHub PRs

-existent dependency listed in solr-core) Jan > 8. des. 2021 kl. 13:55 skrev Jan Høydahl : > >> This is a proposal for a one-time action, introducing a stale-bot for the >> project, which I can see is more controversial and annoying for sure. > > Correcti

Re: Closing GitHub PRs

> This is a proposal for a one-time action, introducing a stale-bot for the > project, which I can see is more controversial and annoying for sure. Correction: This is a proposal for a one-time action, NOT introducing a stale-bot for the project, which I can see is more controversial and

Re: Closing GitHub PRs

, Dec 8, 2021 at 7:01 AM Robert Muir wrote: >>> >>> I added my vote against bulk close functionality. >>> it is pretty clear from this thread that several of us are opposed to >>> bulk close. >>> >>> somehow the discussion jumped from bulk commenting t

Re: Closing GitHub PRs

rev Jan Høydahl : > > +1 to bulk commenting on the 274 open PRs with a standard message about the > need for new PRs. > We already have a "stale-closed" label in GitHub, so if we add that label to > all the issues they can safely be closed without information loss. >

Lucene/Solr 8.11.1 release

Hi, Solr has 13 bug fixes lined up in branch_8_11 already. Lucene has no changes. Now that Lucene 9.0 is out the door (congrats!), let's do the 8.11.1 release. I volunteer as RM and propose a first RC on Monday 13th. That should allow some time to merge any last bug fixes both for Lucene and

Re: Closing GitHub PRs

+1 to bulk commenting on the 274 open PRs with a standard message about the need for new PRs. We already have a "stale-closed" label in GitHub, so if we add that label to all the issues they can safely be closed without information loss. My script

Re: Maven publication with the Gradle build

There may be some loose ends here. See https://issues.apache.org/jira/browse/LUCENE-9809?focusedCommentId=17433373=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17433373 as a starting point for gradle command. Related:LUCENE-10174, Umbrella: LUCENE-9488 So

Re: [VOTE] Release Lucene 9.0.0 RC4

SUCCESS! [0:20:42.942934] +1 Jan > 1. des. 2021 kl. 17:56 skrev Adrien Grand : > > Please vote for release candidate 4 for Lucene 9.0.0 > > The artifacts can be downloaded from: > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.0.0-RC4-rev-0b18b3b965cedaf5eb129aa41243a44c83ca826d > >

Re: Welcome Julie Tibshirani to the Lucene PMC

Welcome, Julie! Jan > 30. nov. 2021 kl. 22:49 skrev Adrien Grand : > > I'm pleased to announce that Julie Tibshirani has accepted an invitation to > join the Lucene PMC! > > Congratulations Julie, and welcome aboard! > > -- > Adrien

Re: [VOTE] Release Lucene 9.0.0 RC3

+1 SUCCESS! [0:23:41.775448] Only ran smoketester this time. Jan > 26. nov. 2021 kl. 15:31 skrev Adrien Grand : > > Please vote for release candidate 3 for Lucene 9.0.0. > > The artifacts can be downloaded from: >

Re: [VOTE] Release Lucene 9.0.0 RC2

+1 SUCCESS! [0:20:30.247277] Ran smoketester and browsed around the archives. Lincense and Notice on top-level of src dist looks good. Tested launching Luke from bin/luke.sh - OK Minor: Luke started on macOS Monterey complains about Times font not being available: > Warning: the fonts "Times"

Re: What should we do of branch_8x?

+1 to remove / lock branch_8x in the lucene-solr repo, i.e. there will not be an 8.12 release by Lucene PMC. Whether Solr needs to release an 8.12 from own repos or not can be discussed in dev@solr if/when needed. So far there is only loose talk, and I think Solr PMC's energy should be devoted

Re: [VOTE] Release Lucene/Solr 8.11.0 RC1

+1 SUCCESS! [1:06:33.517455] Jan > 9. nov. 2021 kl. 21:50 skrev Adrien Grand : > > Please vote for release candidate 1 for Lucene/Solr 8.11.0 > > The artifacts can be downloaded from: >

Re: 8.11 release candidate

I added a PR https://github.com/apache/lucene-solr/pull/2603 for SOLR-14438, that I had in the workings. I think it will do... Jan > 4. nov. 2021 kl. 10:34 skrev Adrien Grand : > > Joel recommended not treating SOLR-15762 as a blocker, so we are left with > the following issues as blockers: >

Re: should we clean up dev-docs?

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:

Re: [VOTE] Release Lucene/Solr 8.10.1 RC1

Ran the smoke tester SUCCESS! [1:21:37.076780] +1 Jan (binding) > 13. okt. 2021 kl. 01:59 skrev Mayya Sharipova : > > Please vote for release candidate 1 for Lucene/Solr 8.10.1 > > The artifacts can be downloaded from: >

Re: Simplify the release artifacts

+1 to all suggestions. ASF has a release policy (https://www.apache.org/legal/release-policy.html#release-distribution) and artifacts must be uploaded to the mirrors. There is also a release distribution policy (https://infra.apache.org/release-distribution.html#download-links) that says

Re: Bugfix release Lucene/Solr 8.10.1

Remember that the releaseWizard on 8x repo is not prepared with correct commands to update the 'main' repos properly. So each time it asks you to do stuff on 'master'/unstable branch you must instead manually adapt andd perform those steps on the new apache/lucene and apache/solr repos. Jan >

Re: Now that 8.10 is out ... let's get rolling on 9!

I don't think the wizard in lucene-solr repo is prepared to check out the new solr.git/main and lucene.git/main to run addVersion and backcompat stuff, so this likely needs to be done manually during an 8.x release? Jan > 30. sep. 2021 kl. 17:25 skrev Timothy Potter : > > I don't know what

Re: Lucene 9.0 release

+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

Re: [VOTE] Release Lucene/Solr 8.10.0 RC1

+1 SUCCESS! [1:09:04.477915] Just ran smoke tester. Jan > 22. sep. 2021 kl. 17:41 skrev Timothy Potter : > > Please vote for release candidate 1 for Lucene/Solr 8.10.0 > > The artifacts can be downloaded from: >

Re: Soften Jira's note when opening new issues?

+1 Jan > 20. sep. 2021 kl. 10:32 skrev Adrien Grand : > > Hello, > > Jira gives the following note when opening an issue: > > ``` > This project has a user mailing list and an IRC channel for support. Please > ensure that you have discussed your problem using one of those resources > BEFORE

Re: New branch and feature freeze for Lucene/Solr 8.10.0

> 17. sep. 2021 kl. 13:46 skrev Robert Muir : > > Sure, but that package is archived/read-only, GPLv3. with 3 watchers and 1 > star. > > On Fri, Sep 17, 2021 at 4:27 AM Jan Høydahl wrote: >> >> Let's just follow the spec and move on. >> >> Just tested

Re: New branch and feature freeze for Lucene/Solr 8.10.0

Let's just follow the spec and move on. Just tested this python package, which has no problem parsing the problematic manifest https://pypi.org/project/jarmanifest/ >>> manifest.getAttributes("/tmp/lucene-manifest.mf") [{'implementationversion': '9.0.0-SNAPSHOT

Re: Welcome Mayya Sharipova to the Lucene PMC

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

Re: Propose changing the "dist" layout

level folder name? Those that are not yet converted can stay in “contribs”? Can we make solr-exporter a separate git repo? With separate artifacts and separate docker image. Don’t know if that means it must also be a full sub project? Jan Høydahl > 11. jun. 2021 kl. 22:46 skrev David Smi

Re: [VOTE] Release Lucene/Solr 8.9.0 RC1

kl. 13:48 skrev Robert Muir : > > Jan, I'm using the same automated smoketester as everyone else. It > fails, so my vote is -1. > > On Fri, Jun 11, 2021 at 7:22 AM Jan Høydahl wrote: >> >> Tested on MacOS (Intel), No other verification than smoketester done &

Re: Propose changing the "dist" layout

+1 to a cleanup here for 9.0. As clean and neat organization as possible. Perhaps rename "dist" -> "lib"? I wish we could get rid of the server (jetty) folder altogether, and move everything from server/solr-webapp/webapp/WEB-INF/lib to "lib/deps/". But that ties into custom boot-class,

Re: [VOTE] Release Lucene/Solr 8.9.0 RC1

Tested on MacOS (Intel), No other verification than smoketester done SUCCESS! [1:08:19.953492] +1 Robert - not sure if one test-run failure should cancel the build. Our smoketester and tests are sometimes a bit picky, and does not mean that the artifacts are faulty. Jan > 11. jun. 2021 kl.

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

ns-slave/workspace/Lucene/Lucene-Solr-SmokeRelease-8.9/lucene/build/smokeTestRelease/tmp/unpack/solr-8.9.0/contrib/gcs-repository/lib/jsr305-3.0.2.jar" > contains sheisty class "javax/annotation/CheckForNull.class" > > Thank you in advance. > > On Fri, Jun 4, 2021

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

so Mayya should weigh in I think. > > Cassandra > On Jun 3, 2021, 5:49 AM -0500, Jan Høydahl <mailto:jan@cominvent.com>>, wrote: >> Mayya, Cassandra, I'd like to merge the Jetty upgrade, SOLR-15316 to >> branch_8x and branch_8_9. See backport PR >> https:

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

Mayya, Cassandra, I'd like to merge the Jetty upgrade, SOLR-15316 to branch_8x and branch_8_9. See backport PR https://github.com/apache/lucene-solr/pull/2502 Is that ok? Jan > 2. jun. 2021 kl. 01:00 skrev Jan Høydahl : > > Cassandra, > > Thanks for spotting the Jetty J

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

orry, I’m way behind on mailing lists and didn’t see the branch had been cut > already! > > Cassandra > On Jun 1, 2021, 3:54 PM -0500, Jan Høydahl , wrote: >> Let's not hold up the release due to this incomplete PR. It obviously needs >> more time for completion and

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

Let's not hold up the release due to this incomplete PR. It obviously needs more time for completion and there is always a new train to catch. As far as I understand, Circuit breakers are pluggable, so anyone can configure their own implementation in the meantime? Jan > 1. jun. 2021 kl. 22:13

Re: Doubling down on our mistakes?

apache.org/thread.html/r9875b53aeaebca8678ee0127562d8a35c7938906fbd318ac17ba011d%40%3Cdev.solr.apache.org%3E <https://lists.apache.org/thread.html/r9875b53aeaebca8678ee0127562d8a35c7938906fbd318ac17ba011d@%3Cdev.solr.apache.org%3E> Jan Høydahl Solr PMC Chair > 21. mai 2021 kl. 05:52

Statement from the Solr and Lucene PMC regarding recent Code of Conduct violations

This is a joint statement on behalf of the Apache Solr and Lucene Project Management Committees (PMCs). Some of the language used in May 2021 on the SOLR-14245 JIRA issue [1] and the concurrent dev@solr [2] and dev@lucene [3] mailing list threads violates our project community's Code of

Re: Welcome Greg Miller as Lucene committer

Welcome, Greg! Jan > 29. mai 2021 kl. 21:47 skrev Adrien Grand : > > I'm pleased to announce that Greg Miller has accepted the PMC's invitation to > become a committer. > > Greg, the tradition is that new committers introduce themselves with a brief > bio. > > Congratulations and welcome! >

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

+1 to a 8.9 release I'm working on a few Solr backports that will land soon. Jan > 12. mai 2021 kl. 09:46 skrev Peter Gromov > : > > I can try backporting Hunspell improvements > (https://issues.apache.org/jira/browse/LUCENE-9687 > ) to

Re: Separate git repo(s) for Solr modules

Folks 1. This is the dev@lucene list, please move discussions over to dev@solr 2. The thread about simultaneous lucene/solr dev is in dev@solr with subject "Proposal to pin the Lucene snapshot version on main" 3. If you want to discuss whether Solr should be a monorepo or multiple repos, start

Re: Moving usage documentation of Luke to Lucene Website

Hi That could be feasible. Have a look at the website git repo at https://github.com/apache/lucene-site. Should be fairly easy to move the Markdown files from github to this site, which also accepts Markdown... Jan > 30. apr. 2021 kl. 08:41 skrev Michael Wechner : > > Hi > > I just noticed

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

Sorry, my vote was +1, forgot to add an explicit +1 to my vote. Jan > 12. apr. 2021 kl. 17:43 skrev Mike Drob : > > It's been >72h since the vote was initiated and the result is: > > +1 5 (Mike Drob, Tim Potter, Anshum Gupta, Bruno Roustant, Ignacio Vera) > 0 2 (Uwe S

Re: Welcome Peter Gromov as Lucene committer

Welcome Peter! > 6. apr. 2021 kl. 19:47 skrev Robert Muir : > > I'm pleased to announce that Peter Gromov has accepted the PMC's invitation > to become a committer. > > Peter, the tradition is that new committers introduce themselves with a brief > bio. > > Congratulations and welcome! >

Re: 9.0 release

Hi, Where are we at with the Lucene 9.0 release planning? The git split is largely done. Not sure about the build. Let's update the umbrella issue https://issues.apache.org/jira/browse/LUCENE-9375 for known remaining cleanup tasks. The one

Re: [NOTICE] Old git branches will be pruned (in lucene.git repo)

Hi all, Today, all the old git branches in lucene.git are gone. If you like to sync up your local git checkout so you don't see those phantom branches, please run this command in your local checkout: git fetch --prune origin Jan > 16. mar. 2021 kl. 16:04 skrev Jan Høydahl : > >

Re: [NOTICE] Old git branches will be pruned (in lucene.git repo)

gt; so "no history is lost" will be true as well. > Having tags for actual releases (e.g. for 8.8, 8.7, etc.) is great for doing > quick IDE comparisons to see how code changed. > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linke

[NOTICE] Old git branches will be pruned (in lucene.git repo)

Hi, With the new lucene.git repo up and running, we (Uwe, Dawid and I) like to get rid of some clutter. We discussed on Slack and later her on list[1] the option of pruning all the 112 old branches. It makes no sense to keep stale branch_x_y branches in lucene.git repo, as any future 8.x or

Re: Branch cleaning/ archiving

s : > > This will also require people who already made their clones/ forks to > prune their copy of the remote as this isn't done automatically. > > git remote prune origin > > Other than that -- looks good to me. > > D. > > On Wed, Mar 10, 2021 at 11:19 PM J

Re: Branch cleaning/ archiving

(?) but the script continues anyway and > proceeds with the delete: > git push ${REMOTE} --delete $BRANCH > > > On Wed, Mar 10, 2021 at 10:35 PM Jan Høydahl <mailto:jan@cominvent.com>> wrote: > Ok, I took a stab at this > > We have 113 branches. Here is a sc

Re: Does CVE-2020-27223 impact Solr 8.6.1

Hi, Please see https://solr.apache.org/security.html for how to handle potential security issues responsibly. From time to time we upgrade our Jetty dependencies, so feel free to file a public JIRA to upgrade Jetty in next release. Normally you'd not be vulnerable to this DoS attach since you

  1   2   3   4   5   6   7   8   9   >