On Mon, Apr 28, 2025 at 09:35:05AM -0300, Athos Ribeiro wrote: > >Currently, users upgrading to a new release never face a feature > >regression, and only face a bugfix regression in some limited > >circumstances[1]. Could you adjust the process and wording to maintain > >this property, please? > > This is not my understanding of this exception. We do have a section in > the end of the exception text where we document all the known > regressions > (https://wiki.ubuntu.com/DockerUpdates#Record_of_regressions). > > Moreover, the introduction text says > > we provide more value to our users by delivering an "upstream" > experience rather than worrying over-much about backward compatibility > or regressions. > > When I discussed this with the previous maintainer (Kanashiro), before I > started working on this stack, he did point out that the idea here would > be to continuously update the stack to the latest upstream version.
I think we're talking about different classes of regression. Consider: User relies on behaviour A; updates from the noble release pocket to noble-updates; gets different behaviour B because Docker upstream changed that behaviour in a major release bump: this is permitted as you point out above. User then upgrades from noble-updates to plucky-updates; behaviour regresses from B back to A because Plucky wasn't treated to the major version bump but only an upstream bugfix branch that didn't include the A->B behaviour change: this should not be permitted. Previously this was prevented by requiring all supported releases to be backport targets. But if you wish to differentiate, then preventing the second case above is a property that I'm saying must still be maintained. Otherwise we end up in a situation where upgrading to a newer Ubuntu release makes things worse. I think this would be really bad for the project, and as long as we have interim (non-LTS) releases, we shouldn't allow this to happen as it would make them pointless. In this case, I suggest we maintain this property by requiring that all newer still-supported series must be bumped with the same or "better" upstream update when performing any SRU. "Better" means something that is inclusive of all relevant changes being made in the other. So in the above example, you wouldn't be permitted to do a major version bump to Noble unless you also did it to Plucky.
signature.asc
Description: PGP signature
-- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release
