Hi all 2.375 is selected as the next baseline.
Thanks Tim On Mon, 31 Oct 2022 at 21:18, Tim Jacomb <[email protected]> wrote: > 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. > > On Fri, 28 Oct 2022 at 14:21, Alexander Brandes <[email protected]> > wrote: > >> 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 >> <https://issues.jenkins.io/browse/JENKINS-69966>. >> 2.372 <https://www.jenkins.io/changelog/#v2.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. >> >> On Tuesday, 25 October 2022 at 17:48:11 UTC+2 [email protected] wrote: >> >>> On Tue, Oct 25, 2022 at 7:42 AM '[email protected]' via Jenkins >>> Developers <[email protected]> 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. >>> >> -- >> 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 on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicRBTV10yOP%3DX%2BwzQoGtCcLixmhqd16d7CQK8O2Fw4GFA%40mail.gmail.com.
