I see; I would kind of like to get the release out before ApacheCon NA, which starts Oct 3. Do you think it's likely AdoptOpenJDK will release its JDK19 in the next week (say by Sep 26)?
On Wed, Sep 21, 2022 at 4:32 AM Uwe Schindler <u...@thetaphi.de> wrote: > > Hi, > > JDK 19 was released yesterday and I am still waiting for AdoptOpenJDK to > publish Gradle Toolchain compatible releases to be available. To me the > schedule is a bit bad: Just on the day of the possibility to add (optional) > support for JDK 19 Panama powered MMAP, we started the release. > > I would really like to have a JDK 19 release that adds support for JDK 19 > preview (it can only be tested for exactly the JDK 19 series, won't work with > JDK 20), so we should have a release including the new code between now and > March (ideally before XMAS). > > Options we have > > Let the 9.4.0 release go out now and add a 9.5.0 in a month or so (I would be > release manager). I do not want to add a bugfix release as theres a small API > change (MMAPDirectory ctor changes from int -> long parameter for chunk > size). We can name this release as the "Java 19 release for early adopters" > Wait a few days and respin the release after > https://github.com/apache/lucene/pull/912 went in? The code is thoroughly > tested by Policeman Jenkins since several months, just the compilation does > not work out of box until theres a Temurin build of OpenJDK 19. > > I just repeat, the above PR does not change any productive code, so it should > be bug-free. It only adds a few class files which are only used when you pass > "--enable-preview" to your JDK. This makes it easy for users to check Solr or > Elasticsearch with JDK 19. No risk, it only activates when you enable it. > > Thoughts? > > Uwe > > Am 02.09.2022 um 21:42 schrieb Michael Sokolov: > > NOTICE: > > Branch branch_9_4 has been cut and versions updated to 9.5 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 to Jira first to give others the chance to review > and possibly vote against the patch. 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 Jira issues with Fix version 9.4 and priority "Blocker" will delay > a release candidate build. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
