Hi Nicolas, Could we hold off on creating the release26.11 branch for a few more days? As agreed in the Java 25 proposal thread, trunk is moving to Java 25 before we branch, and that work is nearly done: the build, CI and Docker changes are merged, the replacement of the Java 17 workarounds is in review, and making compiler warnings fatal is the last step. I'd also like to finish some cleanup in the plugins before the branch, so that 26.11 doesn't start out carrying it.
I expect both to be done by 15 November. After that I'm happy to start the release process and create the branch, unless Michael or you would rather do it, in which case I'll let you know as soon as trunk is ready. Thanks for pushing this forward, Mridul Pathak On Thu, Nov 5, 2026 at 4:09 PM nicolas.malin.nereide.fr via dev < [email protected]> wrote: > Hello Michael, > > Do you have the time to do this ? Otherwise I can process it. > > Nicolas > > Le 02/11/2026 à 09:13, nicolas.malin.nereide.fr via dev a écrit : > > Hello Michael, > > > > Like we planned it, I think you can create the new release branch now. > > > > Nicolas > > > > Le 30/10/2026 à 13:37, Michael Brohl a écrit : > >> Hi everyone, > >> > >> the voting in June has resulted in a plan for the next release branch > >> as you can see below. > >> > >> The initial step would be to create a new release branch in November, > >> followed by a stabilization period an publication of the first > >> release not later than March 2027. > >> > >> I'd like to ask the community if there are any topics which would > >> postpone this plan and how we want to proceed further to create the > >> next release branch? > >> > >> Thanks for your feedback and best regards, > >> > >> Michael Brohl > >> > >> ecomify GmbH - www.ecomify.de > >> > >> Am 30.06.26 um 10:44 schrieb Jacopo Cappellato: > >>> The vote is now closed. > >>> > >>> The vote thread is available at: > >>> https://lists.apache.org/thread/1sq3to1cqybgws678p4wc6oywvm8c01c > >>> > >>> The results are: > >>> > >>> ================================== > >>> Option A (Create a new release branch and set the end-of-life date for > >>> release24.09) > >>> > >>> Number of +1 votes: 22 (including 10 binding votes). No other votes (0 > >>> or -1) were cast for this option. > >>> > >>> Regarding the preferred month for creating the release branch: > >>> * 14 voters specified November 2026. > >>> * 8 voters specified a range of months that includes November 2026. > >>> > >>> ================================== > >>> Option B (Do not set an end-of-life date for release24.09) > >>> > >>> Number of +1 votes: 0. No other votes (0 or -1) were cast for this > >>> option. > >>> > >>> ================================== > >>> > >>> The following actions will be carried out: > >>> > >>> * Create the new release branch in November 2026, named release26.11. > >>> * After an adequate branch stabilization period, publish the first > >>> release from the release26.11 branch no later than March 2027. > >>> * Set the end-of-life date for the release24.09 branch to coincide > >>> with the publication of the first release from the release26.11 > >>> branch, no later than March 2027. > >>> > >>> Thanks to everyone who participated in the discussion and the vote. > > >
