Backporting for LTS 2.462.2 started

[Alexander Brandes]

Hey everyone,

Backporting for 2.462.2 has started, and the RC is scheduled for 2024-08-21.

Candidates: https://issues.jenkins.io/issues/?filter=12146
Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.462.2-fixed
Rejected: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.462.2-rejected

Best regards,

Alex

[Mark Waite]

On Wednesday, August 14, 2024 at 1:48:01 PM UTC-6 Alex Brandes wrote:

Hey everyone,

Backporting for 2.462.2 has started, and the RC is scheduled for 2024-08-21.

I've opened issue JENKINS-73622 proposing to backport Spring Framework 5.3.39 (upgrade from 5.3.37) to Jenkins 2.462.2.  The change won't arrive in Jenkins weekly until Tuesday 20 Aug 2024, the day before the 2.462.2 release candidate, so it is not yet eligible for backport.

As far as I can tell, the backport is low risk and keeps the LTS aligned with the most recent Spring Framework 5.3.x release.  Since Spring Framework 5.3.x has announced that their last build will be in August 2024, I think it is useful to keep ourselves aligned with their most recent releases.

Mark Waite

[James Nord]

https://issues.jenkins.io/browse/JENKINS-73404 is missing from the candidate query as it has no resolution?

[James Nord]

hit sent to early, it has resolution done, but is not matching the query which wants "fixed" (improvements are not fixed, but implemented aka done).

should the query not be 
issuetype in (Bug, Improvement) AND statusCategory = Done AND resolution in (Fixed, Done) AND labels = lts-candidate ORDER BY summary ASC, resolved ASC

[Alexander Brandes]

Indeed, that didn't appear in the query yesterday, given it was still in progress, according to the status. I'll create a follow-up backporting PR later :)

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/mfB-OlJOuCY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2856e080-4760-4d0d-b2d8-5547bdf3c797n%40googlegroups.com.

[Mark Waite]

On Thursday, August 15, 2024 at 8:25:15 AM UTC-6 James Nord wrote:

hit sent to early, it has resolution done, but is not matching the query which wants "fixed" (improvements are not fixed, but implemented aka done).

should the query not be 
issuetype in (Bug, Improvement) AND statusCategory = Done AND resolution in (Fixed, Done) AND labels = lts-candidate ORDER BY summary ASC, resolved ASC

I think that you're right that the query should be extended to include "Done".  As a workaround, I reopened the issue, set its resolution as "Fixed", and closed the issue.

It is now in the list of LTS candidates for consideration.

[Mark Waite]

I've opened issue JENKINS-73648 proposing to backport Spring Security 5.8.14 (upgrade from 5.8.13) to Jenkins 2.462.2.  The change won't arrive in Jenkins weekly until Tuesday 20 Aug 2024, the day before the 2.462.2 release candidate, so it is not yet eligible for backport.

As far as I can tell, the backport is low risk and keeps the LTS aligned with the most recent Spring Security 5.8.x release.  Since Spring Security 5.8.x has announced that their last build will be in August 2024, I think it is useful to keep ourselves aligned with their most recent releases.

[Basil Crow]

+1

[Basil Crow]

While we're at it, we may want to also backport JUnit plugin version
1291.v60776881903c, since the lack of
https://github.com/jenkinsci/junit-plugin/pull/638 might cause
problems for some scanners as well.

[Alexander Brandes]

Good catch, Basil! I have included the commit mentioned