Next LTS baseline selection

[Cathy Chan]

Hi all,

Looking at the Jenkins events calendar, we should have been well underway with the selection of the next LTS baseline.

Any proposals?

- Cathy.

[Basil Crow]

I feel strongly that the following fixes be included in the next LTS release:

jenkinsci/jenkins#7208 - Fix for weather icon issue that many users
have complained about (included in the forthcoming 2.375)
jenkinsci/jenkins#7270 - Important fix for Java 17 users (included in
the forthcoming 2.375)
jenkinsci/jenkins#7273 - Fix for regression in queue maintenance
introduced in 2.361 (included in the forthcoming 2.375)
jenkinsci/jenkins#7275 - Update bundled plugins with security fixes
(included in the forthcoming 2.375)
jenkinsci/jenkins#7277 and jenkinsci/winstone#296 - Fix for WebSocket
regression introduced in the last LTS that many users have complained
about (included in the forthcoming 2.375)
jenkinsci/jenkins#7286 - Fix for regression in safe restart page
introduced in 2.374 (included in the forthcoming 2.375)

Based on the above 2.375 could make a good candidate. Note that 2.375
also contains a number of significant frontend changes that have not
yet received widespread adoption:

jenkinsci/jenkins#6912 - Improve breadcrumb bar accessibility
jenkinsci/jenkins#7049 - Update the design of notifications
jenkinsci/jenkins#7197 - Update design of Manage Users page

Assuming that no issues with the abovementioned regression fixes and
frontend changes are discovered next week, my vote would be for 2.375.

[Alexander Brandes]

+1 for 2.375

[wfoll...@cloudbees.com]

FTR 2.375 was released ~4h ago, the changelog page is not even updated (to receive the feedback).

With the list of regression/bug fix it seems to be a good candidate, but I think we should monitor carefully the user feedbacks and be ready to provide backports to a previous version.

To ease this kind of discussion, it could be interesting to introduce only very minor features or bug fixes before the LTS selection, so that we have more time to test them. But it's a different topic :p

[Basil Crow]

On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
Developers <jenkin...@googlegroups.com> wrote:
>
> To ease this kind of discussion, it could be interesting to introduce only very minor features or bug fixes before the LTS selection, so that we have more time to test them. But it's a different topic :p

FTR there is something written about this at
https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
although it refers more to security releases than creating a new
stable branch. But yes I personally would not have merged the
abovementioned three frontend changes so close to the branching date.
If any issues are discovered in the next week, we can revert the
relevant commits from the stable branch, or create the stable branch
from an earlier point and backport the bug fixes to it like you
mentioned.

[Alexander Brandes]

As an alternative to 2.375, I'd like to bring up 2.372 as a possible candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966.

2.372 is a much less recent weekly release, with a better rating than 2.375 and less big changes, which could result in possible regressions. It was released almost a month ago with no community reported issues, according to the changelog.

[Tim Jacomb]

https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue, but it has a fix on the plugin so I wouldn't worry too much about it.

2.375 looks to be a good baseline to me.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%40googlegroups.com.

[Tim Jacomb]

Hi all

2.375 is selected as the next baseline.

Thanks

Tim