First it seems a bit short notice to give that warning a week before the
milestone, even if the current report indicates there should be no
practical issue it would be nice to have such changes discussed more in
advance in the futur
And I've also some questions
1. Are we confident those issues are currently visible to owning teams?
I think only the uploader get notified today, maybe it would make sense
to also reports bugs and tag those rls-...-incoming as we do for archive
rebuilds?
2. Are you going to make stakeholders part of the decision process and
if so how?
3. If you decide to revert back to the previous version, what does it
mean for users who already got the upgrade? Do we let them on a version
we decided was buggy and should be reverted? If that's the case
shouldn't we try to rather bump the revision to something newer to
ensure everyone is moved out the buggy version?
Cheers,
Sebastien Bacher
Le 26/07/2022 à 01:05, Brian Murray a écrit :
> With the imminent point release of Ubuntu 22.04 LTS, I wanted to let
> everyone know of an addition to the point release process[1] followed by
> the Ubuntu Release team.
>
> The team will evaluate the packages currently phasing[2] which are also
> on any installation media and make a decision as to whether the packages
> should be fully phased or if the package should be reverted back to the
> prior version.
>
> The point of doing this is to ensure that we are not creating an image
> (and subsequently an installed system) with a package version which
> contains a regression in that package.
>
> [1] https://wiki.ubuntu.com/PointReleaseProcess
> [2] https://people.canonical.com/~ubuntu-archive/phased-updates.html
>
> Thanks,
> --
> Brian Murray
> on behalf of the Ubuntu Release Team
>
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
