Update CHANGES.txt to reflect my optimization PR 15637

[countmdm]

Description

Update CHANGES.txt as requested by reviewers of my PR 15637.

[shubhamsrkdev]

I think there is already a CHANGES.txt entry (targeting 10.5) for #15637 . I think @dweiss added it for your PR?

[countmdm]

I think there is already a CHANGES.txt entry (targeting 10.5) for #15637 . I think @dweiss added it for your PR?

I am somewhat confused by how to keep track of all Lucene branches. But to the best of my knowledge, no, there is no entry for #15637. @dweiss once added an entry for my previous PR, #15618 .

[dweiss]

You should add a changes entry to the section/ version against which the patch is targeted, for example:
https://github.com/apache/lucene/blob/main/lucene/CHANGES.txt#L196

This is applied to branch_10x, then forward-ported to main (or applied to main and then backported to 10x) but it'll be consistent on both.

[countmdm]

You should add a changes entry to the section/ version against which the patch is targeted, for example: https://github.com/apache/lucene/blob/main/lucene/CHANGES.txt#L196

This is applied to branch_10x, then forward-ported to main (or applied to main and then backported to 10x) but it'll be consistent on both.

Ok, I see. The CHANGES.txt file on the above link has a "Lucene 10.5.0" section. However, on my local main branch, this file only has "Lucene 11.0" and "Lucene 10.4.0" sections.

You should add a changes entry to the section/ version against which the patch is targeted, for example: https://github.com/apache/lucene/blob/main/lucene/CHANGES.txt#L196

This is applied to branch_10x, then forward-ported to main (or applied to main and then backported to 10x) but it'll be consistent on both.

Oh, ok, sorry about myself being dumb, I forgot to update my Lucene fork :) Now I see that there is already a proper entry in CHANGES.txt for #15637 . So closing this PR.