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 On Thursday, August 15, 2024 at 3:19:53 PM UTC+1 James Nord wrote: > https://issues.jenkins.io/browse/JENKINS-73404 is missing from the > candidate query as it has no resolution? > > > On Thursday, August 15, 2024 at 3:04:59 PM UTC+1 Mark Waite wrote: > >> 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 >> <https://issues.jenkins.io/browse/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 >> <https://spring.io/blog/2024/03/01/support-timeline-announcement-for-spring-framework-6-0-x-and-5-3-x>, >> >> I think it is useful to keep ourselves aligned with their most recent >> releases. >> >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/dbb9ff3e-dfdc-4068-acf8-c115679f634fn%40googlegroups.com.
