Yes

On Mon, 17 Jul 2023 at 19:47, Mark Waite <[email protected]> wrote:

>
>
> On Monday, July 17, 2023 at 9:41:51 AM UTC-6 Basil Crow wrote:
>
> There do not appear to be any known user-visible regressions in production
> code in 2.414, but jenkinsci/jenkins#7872
> <https://github.com/jenkinsci/jenkins/pull/7872> implies a change in
> Login Theme (3,757 installations) which has not yet been completed (tracked
> in JENKINS-71238 <https://issues.jenkins.io/browse/JENKINS-71238>) and
> jenkinsci/jenkins#7942 <https://github.com/jenkinsci/jenkins/pull/7942>
> implies a change in Calendar View (1,866 installations) which has not yet
> been completed (tracked in JENKINS-71663
> <https://issues.jenkins.io/browse/JENKINS-71663>). If these tasks are not
> completed by the time 2.414 LTS ships, they should be documented as known
> defects in the release notes.
>
>
> Thanks for noting those needed additions to the upgrade guide.  Since
> those changes are in Jenkins 2.413 and in Jenkins 2.414, it makes sense to
> me that we choose Jenkins 2.414.
>
> Tim Jacomb, do you agree that Jenkins 2.414 should be the baseline for the
> LTS release scheduled for August 23, 2023?
>
> 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 on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/2fad8aa3-2774-413d-b41b-1f2e1ee1a94dn%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/2fad8aa3-2774-413d-b41b-1f2e1ee1a94dn%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-3BidBb0eaiecRCwTJvSfSJrddA9bsLa70fzsM1Bj7z0zCew%40mail.gmail.com.

Reply via email to