This vote is a follow-up to the discussion in the thread "Proposal to backport Tomcat 10 / Jakarta migration to release24.09".
With this vote, we will either set an end-of-life date for release24.09 no later than March 2027, which could coincide with the publication of the first release from a new release branch, or backport the Jakarta migration (and any other relevant changes) to allow us to continue using Tomcat and other external dependencies safely in the release24.09 branch, relying only on dependencies that are actively maintained. Please vote: ============================================= A) Create a new release branch and set the end-of-life date for release24.09 no later than March 2027. By voting +1 for this option, if you wish, please specify the month, or range of months, between June 2026 and March 2027 in which you would like the release branch to be created. The stabilization period will be decided later through a separate vote; however, the first release will be published no later than March 2027. For example: By voting "+1, July-September", you are indicating that you would like the new release branch to be created in July, August, or September (e.g. release26.07, release26.08, or release26.09). ============================================= B) Do not set an end-of-life date for release24.09. By voting +1, you prefer that we do not set an end-of-life date for release24.09 and that we accept backporting the Jakarta migration and similar changes to extend its lifetime. Note that backporting the Jakarta migration may affect custom projects based on release24.09, as they may need to migrate custom code to Jakarta within a short period of time. ============================================= Jacopo
