On Tue, Apr 26, 2022 at 8:25 PM Kevin Kofler via devel
<devel(a)lists.fedoraproject.org> wrote:
> 4. This is not a policy, but just a guide, an outdated one.
Updates
> policy does not require maintainers to use side tags in this case.
The Updates Policy is not relevant for Rawhide. What is relevant is that
Rawhide rules have become much stricter than in the past and that it is no
longer allowed to just break Rawhide. I am not a fan of the new rules either
(and I have speaken out against them more than once), but they are there,
and infrastructure has been depending on them for months already (e.g.,
these days, if there is a broken dependency in any release-critical
deliverable, the whole Rawhide compose fails and everything stands still,
nothing gets delivered to mirrors at all until it is fixed, which in turn
prevents third-party repositories from rebuilding their packages against
both your and other simultaneous Rawhide changes). So if you are unhappy
about the rules, please help getting them changed, but do not just ignore
them.
Updates policy does apply to rawhide too. There is even a section
specific to rawhide.
--
Mikolaj Izdebski
Kevin Kofler
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure