Backporting for LTS 2.568.1 started

[Kris Stern]

Hi everyone,

Backporting for 2.568.1 has started.  The Release Candidate (RC) is scheduled for 2026-06-24.

Candidates: closed issues and open issues
Fixed: Issues
Rejected: Issues

Best regards,
Kris Stern

[James Nord]

Hi all,

the searches used to obtain candidates do not seem correct, according to the PR template you can label a PR with `lts-candidate` but only issues are looked at?

eg. https://github.com/jenkinsci/jenkins/pull/26883 is marked as lts-candidate.

additionally https://github.com/jenkinsci/jenkins/pull/26819 was backported previously but did not get the lts-fixed label?

There are a few PRs with the label that appear to be either already included due to the baseline, or have been picked due to a meta issue created after the fact.

Regards

/James

[Mark Waite]

On Wed, Jun 24, 2026 at 5:12 AM 'James Nord' via Jenkins Developers <jenkin...@googlegroups.com> wrote:

Hi all,

the searches used to obtain candidates do not seem correct, according to the PR template you can label a PR with `lts-candidate` but only issues are looked at?

The LTS release checklist includes links for candidate issues and candidate pull requests.  The email did not include those links, but they are in the checklist.

 

eg. https://github.com/jenkinsci/jenkins/pull/26883 is marked as lts-candidate.

additionally https://github.com/jenkinsci/jenkins/pull/26819 was backported previously but did not get the lts-fixed label?

There are a few PRs with the label that appear to be either already included due to the baseline, or have been picked due to a meta issue created after the fact.

When releasing 2.555.3, we mistakenly failed to update the labels for some backported issues.  I've corrected that mistake.

Mark Waite

[James Nord]

>  The LTS release checklist includes links for candidate issues and candidate pull requests.  The email did not include those links, but they are in the checklist.

Thanks Mark

is there a reason then why https://github.com/jenkinsci/jenkins/pull/26883 was not included or explicitly rejected in https://github.com/jenkinsci/jenkins/pull/26987? Anything I should be doing differently?

/James

[Mark Waite]

On Wed, Jun 24, 2026 at 5:48 AM 'James Nord' wrote:

>  The LTS release checklist includes links for candidate issues and candidate pull requests.  The email did not include those links, but they are in the checklist.

Thanks Mark

is there a reason then why https://github.com/jenkinsci/jenkins/pull/26883 was not included or explicitly rejected in https://github.com/jenkinsci/jenkins/pull/26987? Anything I should be doing differently?

You caught us in the midst of a transition.  When we used Jira for issue tracking, we required that all backports have a corresponding Jira issue.  That ensured we had a Jira issue that could be referenced in the Jenkins LTS changelog.  Since we've changed to tracking issues with GitHub, we've been able to relax that requirement.

Unfortunately, some of our queries had not yet adapted to the relaxed requirement that the `lts-candidate` label can be applied to either an issue or a pull request.

In this case, I missed the label when creating a local prototype of the stable-2.568 branch and Kris missed the label when creating the official 2.568.1 backport pull request.  Kris and I weren't working together on it, yet we both missed the label.  The query in the LTS release checklist template has been updated in hopes that we won't make that mistake in the future.

I've cherry picked that commit into the backporting pull request as https://github.com/jenkinsci/jenkins/pull/26987/changes/034a47832e76429f3cf0fe7996300fe5ac1797cc 

Mark Waite