On Fri, Nov 13, 2020 at 12:23:05AM +0100, Kevin Kofler via devel wrote:
> Kevin Fenzi wrote:
> > The one actual proposed change is to allow releng to untag builds that
> > have already gone out in rawhide composes. This was forbidden by the
> > existing policy.
>
> Worded like in the above quote: Finally!
>
> But when I see the actual wording in the proposed changes, I see that we go
> from an undocumented policy to never untag packages in Rawhide (at least,
> not documented anywhere in the current Update Policy – I think it was
> decided in some FESCo meeting and never actually codified in the
> documentation) to a documented policy to almost never untag packages in
> Rawhide ("it will normally not be untagged"), only "in exceptional cases",
> which is very open to interpretation.
Yep. IMHO it should still be a very rare thing.
Perhaps we should come up with a list of the cases under which it would
happen, but I figured leaving it to releng would be ok.
> Hence, I disagree with the wording in the new policy and still ask for the
> "Rawhide must never go backwards in EVR" policy to be completely overturned,
> not just softened with exceptions. There is simply no rationale for it, with
> distro-sync being a thing, and considering that updates-testing, which is
> supposed to be *more* stable than Rawhide, *can* actually go backwards in
> EVR (and that's a good thing).
We have been over this. If anyone could untag anything they felt like it
would make it much more difficult for everyone to integrate their
changes with the rest of the collection.
kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
