Re: critpath approval process seems rather broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kevin Fenzi wrote:
> Related to this, fesco wanted to look at some changes for security
> updates for stable releases:
> 
> https://fedorahosted.org/bodhi/ticket/581
> 
> Hopefully something like this would help the above case.

While I welcome those changes, I don't understand why we need to make the 
update rules to be enforced by Bodhi more and more complicated (and in fact, 
too complicated for Bodhi to implement correctly, there are already several 
corner cases in which the implementation in Bodhi differs from what FESCo 
requested) when we could just ask maintainers for a bit of common sense and 
do without any software enforcement.

As you're seeing from all those proposals being floated for various special 
cases, there are many factors to consider in the tradeoff between getting 
important fixes out quickly and getting changes tested. I think there's a 
lot to gain from being flexible. No hardcoded policy will do the right thing 
in all cases. This thread is just one of the many cases where it goes wrong.

Homo sapiens sapiens has an organ called the "brain", which is very 
effective at making decisions. We have many of those available, one per 
maintainer. Why not use this processing power for decision making?

        Kevin Kofler

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux