Mailing List Archive: New branch and feature freeze for Lucene 9.7.0

New branch and feature freeze for Lucene 9.7.0

Jun 16, 2023, 4:50 AM

Post #1 of 3 (136 views)

NOTICE:

Branch branch_9_7 has been cut and versions updated to 9.8 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 submit all patches you
want to commit as pull requests first to give others the chance to review
and possibly vote against them. Keep in mind that it is our
main intention to keep the branch as stable as possible.
* All patches that are intended for the branch should first be committed
to the unstable branch, merged into the stable branch, and then into
the current release branch.
* Normal unstable and stable branch development may continue as usual.
However, if you plan to commit a big change to the unstable branch
while the branch feature freeze is in effect, think twice: can't the
addition wait a couple more days? Merges of bug fixes into the branch
may become more difficult.
* Only Github issues with Milestone 9.7
and priority "Blocker" will delay a release candidate build.

--
Adrien

Re: New branch and feature freeze for Lucene 9.7.0 [ In reply to ]

uwe at thetaphi

Jun 16, 2023, 5:52 AM

Post #2 of 3 (136 views)

Permalink

Hi,

I also downloaded latest JDK 21 EA build (21-b27) and regenerated the
apijar files: No changes. So all fine! I did this because there were
some late changes to javadocs and API definition, but it all looks fine.
Also the bug with SecurityManager that hit Elasticsearch was also fixed
(but we have a workaround).

I will now also update Policeman Jenkins to latest EA build.

Uwe

Am 16.06.2023 um 13:50 schrieb Adrien Grand:
> NOTICE:
>
> Branch branch_9_7 has been cut and versions updated to 9.8 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 submit all patches you
> want to commit as pull requests first to give others the chance to
> review
> and possibly vote against them. Keep in mind that it is our
> main intention to keep the branch as stable as possible.
> * All patches that are intended for the branch should first be committed
> to the unstable branch, merged into the stable branch, and then into
> the current release branch.
> * Normal unstable and stable branch development may continue as usual.
> However, if you plan to commit a big change to the unstable branch
> while the branch feature freeze is in effect, think twice: can't the
> addition wait a couple more days? Merges of bug fixes into the branch
> may become more difficult.
> * Only Github issues with Milestone 9.7
> and priority "Blocker" will delay a release candidate build.
>
> --
> Adrien

--
Uwe Schindler
Achterdiek 19, D-28357 Bremen
https://www.thetaphi.de
eMail:uwe@thetaphi.de

Re: New branch and feature freeze for Lucene 9.7.0 [ In reply to ]

christopher.hegarty at elastic

Jun 16, 2023, 7:33 AM

Post #3 of 3 (136 views)

Permalink

Hi Uwe,

> On 16 Jun 2023, at 13:52, Uwe Schindler <uwe@thetaphi.de> wrote:
>
> Hi,
>
> I also downloaded latest JDK 21 EA build (21-b27) and regenerated the apijar files: No changes. So all fine! I did this because there were some late changes to javadocs and API definition, but it all looks fine. Also the bug with SecurityManager that hit Elasticsearch was also fixed (but we have a workaround).
>
> I will now also update Policeman Jenkins to latest EA build.
>
Thanks for verifying the apijar, and adding the new EA build to the Jenkins.

It would be great if we could automate the apijar check, by periodically running a job that sucks down the latest EA build and runs the generation, comparing against the checked in version. But the way we do this already kinda minimises the risk - as you have said before (and I agree), it is very unlikely that the API will change during rampdown.

-Chris.
> Uwe
>
> Am 16.06.2023 um 13:50 schrieb Adrien Grand:
>> NOTICE:
>>
>> Branch branch_9_7 has been cut and versions updated to 9.8 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 submit all patches you
>> want to commit as pull requests first to give others the chance to review
>> and possibly vote against them. Keep in mind that it is our
>> main intention to keep the branch as stable as possible.
>> * All patches that are intended for the branch should first be committed
>> to the unstable branch, merged into the stable branch, and then into
>> the current release branch.
>> * Normal unstable and stable branch development may continue as usual.
>> However, if you plan to commit a big change to the unstable branch
>> while the branch feature freeze is in effect, think twice: can't the
>> addition wait a couple more days? Merges of bug fixes into the branch
>> may become more difficult.
>> * Only Github issues with Milestone 9.7
>> and priority "Blocker" will delay a release candidate build.
>>
>> --
>> Adrien
> --
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de <https://www.thetaphi.de/>
> eMail: uwe@thetaphi.de <mailto:uwe@thetaphi.de>