> On 4. Feb 2026, at 00:34, 'Jesse Glick' via Jenkins Developers
> <[email protected]> wrote:
>
> Call a trunk release 2026.04.20 and you can release on any day you choose,
> not bound by a weekly schedule. If you cut a maintenance branch from that,
> its releases would be 2026.04.20.1, 2026.04.20.2, etc. The next “LTS” line (I
> would debate the accuracy of the “long-term” phrasing) would be something
> like 2026.07.16.x.
Lacking certainty over what the next version number is going to be and adding
an additional version segment both seem like changes requiring rework around
the actual releases (update-center, changelog generator, etc.) for unclear
benefits. Additionally it would prevent regression fix re-releases the same
day. Out of all the options discussed here, this looks like the least desirable.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/jenkinsci-dev/29C8196F-09A4-40DD-A334-000EA0849723%40beckweb.net.
