Bug 2133940 was an ask for the now existing backports to Jammy and Focal to be promoted. It is nice that all that was prepared, but per line 32-35 in [1] this is more than we'd need and to keep things together I've made it a duplicate.
The project has continued to be actively maintained since the promotion which is great to see. Furthermore everything was updated to be on the same version across releases: wsl-pro-service | 0.1.18~20.04.2 | focal-updates/universe | source, amd64, arm64 wsl-pro-service | 0.1.18~22.04.2 | jammy-updates/universe | source, amd64, arm64 wsl-pro-service | 0.1.18~24.04.3 | noble-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x wsl-pro-service | 0.1.18~25.04 | plucky-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x wsl-pro-service | 0.1.18 | questing | source, amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x wsl-pro-service | 0.1.18 | resolute | source, amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x There was no exclusion from older releases in the initial review, on the contrary we expected it, but it was not available yet. That is now resolved via the SRUs in bug 2107145. I compared what we have in J/F/N/devel. I see some adaptations for the backport, mostly around testing (d/get- gepends-go-bin-patch.sh, testdata) and the different dependencies (d/control). I think some of the differences are cosmetic and could be eliminated in the future, but none is a blocking factor to also promoting it in F/J. And it heavily depends on how that was branched and developed. Then from Noble -> Focal I see a clear "base on one and adapt as needed" which is easier to read. Mostly compat level and Go 1.22 + dependencies, the latter causing a lot of noise in the vendoring, but that was to be expected. And finally Focal -> Jammy, that surprised me as it was using the newer golang - but it makes sense once checking toolchain availability. Noble->Jammy is therefore even calmer. Verdict: - These backports were expected - Promoting them was not ruled out for $oldreasons in the past - The content is the same across releases (with backport delta) nowadays - Testing and ownership kept active as promised. => With that it is ok to also promote the package in Jammy and Focal. Please go ahead and make the seed or dependency changes to pull the package in, and then it can be promoted. [1]: https://documentation.ubuntu.com/project/MIR/mir-reporters- template/ ** Changed in: wsl-pro-service (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: wsl-pro-service (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052495 Title: [MIR] wsl-pro-service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-service/+bug/2052495/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
