I thought the proposal was the second number was just a release number which roughly maps to a week but we can and do sometimes release multiple versions in a week for a serious regression or for a release failure
On Sun, 1 Feb 2026 at 10:50, Jenkins Developers < [email protected]> wrote: > During the 2026 Jenkins Contributor Summit in Brussels, Jan 30, 2026, one > of the ideas that was discussed was a possible switch from 2.x based > versions to versions based on the year of the release. The second field of > the version number would be the week of the year and the third field of the > version number would continue to be the version number within the LTS > baseline. > > Some examples: > > - 2.541 would be 2025.50 > - 2.541.1 would be 2025.50.1 > - 2.545 would be 2026.1 > > Benefits: > > - Administrators and users have a clear indicator of the age of their > version > - If we wait until the UX changes are ready (6 months or more from > now), it would be a good indicator that we made a significant change, > without the need to explain that we are not using semantic versioning > > Challenges: > > - Administrators with scripts that are hard coding 2. will need to > adapt > - Window installer may need to map the new version numbers into the > Windows installer version number limitations > > Comments, concerns, and suggestions are welcomed. > Mark Waite > > -- > 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/a5d34387-9454-4a5e-91ac-3618d8dce398n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a5d34387-9454-4a5e-91ac-3618d8dce398n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAH-3Bif4HSaSp922HKZW3-NVKQ7OrZyqXkJC1%2BE5GDU%2B%3DEpFMg%40mail.gmail.com.
