Jeremie Playout and I have started the Jenkins 2.492.1 LTS release checklist. Jeremie is out of office due to illness. I'm sending this message on his behalf.
The release candidate is scheduled for Wednesday 22 Jan 2025, but there are test failures on the Windows configuration of the master branch <https://ci.jenkins.io/job/Core/job/jenkins/job/master/6951/testReport/> and on the Windows configuration of the stable-2.492 <https://ci.jenkins.io/job/Core/job/jenkins/job/stable-2.492/lastCompletedBuild/testReport/> and stable-2.479 <https://ci.jenkins.io/job/Core/job/jenkins/job/stable-2.479/lastCompletedBuild/testReport/> branches. Since those failures happen on stable-2.479 and stable-2.492, I don't think that they are a serious risk to the release candidate build. They do not happen consistently on my local Windows 10 computers. One of the tests fails for me locally about 50% of the time with a test timeout, while on ci.jenkins.io both tests seem to fail consistently on Windows and pass consistently on Linux. I plan to do more investigation of those test failures but don't plan to allow them to block the release candidate build. Backporting links: Candidates: https://issues.jenkins.io/issues/?filter=12146 Fixed: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.492.`-fixed <https://issues.jenkins.io/issues/?jql=labels%20%3D%202.492.1-fixed> Rejected: https://issues.jenkins.io/issues/?jql=labels%20%3D%202.492.1-rejected Best regards, Jeremie Playout and 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/3c2805ec-4b87-43cf-a303-80ffd39756aen%40googlegroups.com.
