Re: [VOTE] Release Lucene 9.9.0 RC1

SUCCESS! [1:03:54.880200] +1. Thank you Chris! On Wed, Nov 29, 2023 at 8:45 PM Nhat Nguyen wrote: > SUCCESS! [1:11:30.037919] > > +1. Thanks, Chris! > > On Wed, Nov 29, 2023 at 8:53 AM Chris Hegarty > wrote: > >> Hi, >> >> >> Please vote for release candidate 1 for Lucene 9.9.0 >> >> >> The ar

Re: [VOTE] Release Lucene 9.9.0 RC1

SUCCESS! [1:11:30.037919] +1. Thanks, Chris! On Wed, Nov 29, 2023 at 8:53 AM Chris Hegarty wrote: > Hi, > > > Please vote for release candidate 1 for Lucene 9.9.0 > > > The artifacts can be downloaded from: > > > https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC1-rev-92a5e5b02e0e083

[VOTE] Release Lucene 9.9.0 RC1

Hi, Please vote for release candidate 1 for Lucene 9.9.0 The artifacts can be downloaded from: https://dist.apache.org/repos/dist/dev/lucene/lucene-9.9.0-RC1-rev-92a5e5b02e0e083126c4122f2b7a02426c21a037 You can run the smoke tester directly with this command: python3 -u dev-tools/scripts/smokeT

New branch and feature freeze for Lucene 9.9.0

Hi Lucene Devs, Branch branch_9_9 has been cut and versions updated to 9.10 on stable branch. Please observe the normal rules: * No new features may be committed to the branch. * Documentation patches, build patches and serious bug fixes may be committed to the branch. However, you should su

Re: Lucene 9.9.0 Release

Hi Feng, > On 29 Nov 2023, at 11:25, Guo Feng wrote: > > Hi Chris, > > Nightly benchmark shows that #12699 gets back some speed. I've backport it to > 9.9.0. I think it is ready now. Awesome! > Sorry for delaying the release! No apology needed. I appreciate your speedy work here. I’ll star

Re: Lucene 9.9.0 Release

Hi Chris, Nightly benchmark shows that #12699 gets back some speed. I've backport it to 9.9.0. I think it is ready now. Sorry for delaying the release! Feng On 2023/11/28 08:32:59 Chris Hegarty wrote: > Hi Guo, > > Thanks for the update. > > Let’s push the 9.9.0 branch cut until tomorrow (ra

Re: GitHub issues vs PRs vs Lucene's CHANGES.txt

Oh, and that the CHANGES.txt entries in e.g. 9.9.0 section match on 9.x and main branches... I think that one we have some automation to catch? Mike McCandless http://blog.mikemccandless.com On Wed, Nov 29, 2023 at 5:58 AM Michael McCandless < luc...@mikemccandless.com> wrote: > Hi Team, > > I

GitHub issues vs PRs vs Lucene's CHANGES.txt

Hi Team, I see Chris is tagging issues that were left open after their linked PRs were merged (thanks!). Is there something in our release tooling that cross-checks all the weakly linked metadata today: Milestone marked (or more often: not) on an issue vs commits to the respective branches vs loc

Re: [JENKINS] Lucene-9.x-Linux (64bit/hotspot/jdk-19) - Build # 14180 - Failure!

JVM crashed: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f9fa8545493, pid=2982126, tid=2990096 # # JRE version: OpenJDK Runtime Environment (19.0+36) (build 19+36-2238) # Java VM: OpenJDK 64-Bit Server VM (19+36-2238, mixed mode, sharing, ti

Re: GDPR compliance

To the valid point Robert makes above about the underlying data still on the disk (old news): https://news.sophos.com/en-us/2022/09/23/morgan-stanley-fined-millions-for-selling-off-devices-full-of-customer-pii/ On Wed, Nov 29, 2023 at 11:01 AM Michael Sokolov wrote: > Another way is to ensure th

Re: GDPR compliance

Another way is to ensure that all documents get updated on a regular cadence whether there are changes in the underlying data or not. Or, regenerating the index from scratch all the time. Of course these approaches might be more costly for an index that has intrinsically low update rates, but they