2.263 is available (and has been for awhile) it’s called bom-latest in the folder structure
And is available under the 2.263.x artifact ID Thanks Tim On Mon, 28 Dec 2020 at 19:27, Mark Waite <mark.earl.wa...@gmail.com> wrote: > > > On Mon, Dec 28, 2020 at 11:10 AM Radek Antoniuk <radek.anton...@gmail.com> > wrote: > >> >>>> Since the selection took place and I can see 2.263.1 in >>>> https://www.jenkins.io/changelog-stable/, shouldn't I see 2.264.x in >>>> https://github.com/jenkinsci/bom ? >>>> >>>> >>> I think that you will eventually see 2.263.x in the bom rather than >>> 2.264.x. I'm sure that a pull request would be welcomed to include 2.263.x >>> in the bom. >>> >> >> >> That was indeed a typo, I meant 2.263.x. >> >> Sure, I'm happy to open a PR but... my question was rather about if the >> LTS release process should automatically mean that a respective PR should >> be opened to the bom repository by the release manager who created the LTS >> release? >> In my case, I'm actually waiting for that since that blocks a dependency >> update (although I actually expected 2.264.x be next LTS, not sure why >> 2.263 was preferred). >> >> > Adding a new release to the plugin BOM is part of the new LTS release > checklist that is being developed by Tim Jacomb. See > https://github.com/jenkins-infra/release/pull/122 for the initial pull > request and https://github.com/jenkins-infra/release/issues/123 for the > first use as preparation for Jenkins 2.263.2. > > Jenkins 2.263 was specifically chosen because it did not include the > significant changes that were introduced in 2.264. Those significant > changes are described in > https://www.jenkins.io/blog/2020/11/10/major-changes-in-weekly-releases/ > and in https://www.jenkins.io/blog/2020/11/10/spring-xstream/ . We > wanted 3 months to work on the changes introduced in 2.264 before they were > delivered to LTS users as part of the March 2021 LTS release. > > 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/CAPe2pWiZWEXzxb0LMKN%3D4QLf_FDegpxB5LE4%3D0RqPv3rA7DKWw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPe2pWiZWEXzxb0LMKN%3D4QLf_FDegpxB5LE4%3D0RqPv3rA7DKWw%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG3qYr4Wgxkp%3DCF%2B1Q-h0mtAQM5Y1zfc3bxuHqYiU%3DyZg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG3qYr4Wgxkp%3DCF%2B1Q-h0mtAQM5Y1zfc3bxuHqYiU%3DyZg%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifyfpfBoe%2BcD82zZGbv%2BbE-dH-CNdCA9_z8%2B1C-HYW-Lg%40mail.gmail.com.
