Kevin Fenzi wrote:
> I disagree. I think we need gating to block as much stuff that breaks
> things from landing as we can and then we should find that keeping
> composes going is much easier on all of us. Then things can be fixed
> when gating catches them and it's on the person who broke things.
And that is going to make development completely cringe to a halt. It is the
nature of a distribution branch under development that things will sometimes
be completely broken for a couple weeks. There needs to be a place to do
development that can cause such temporary breakage.
The side tag approach already does not scale, as evidenced by this thread.
Forcing every small breakage into a side tag is going to make this issue
much worse. All the merge conflicts can be avoided if development is simply
done together in one place.
The purpose of Rawhide should be only and purely to develop future versions
of the distribution. If it accidentally happens to be usable at some point
in time, that is pure luck and no sane user should ever rely on that.
Kevin Kofler
_______________________________________________
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
