On 11/05/2012 07:52 PM, Miloslav Trmač wrote:
A crit path update that affects, say, two packages and nothing else,
could be "approved by default" as well. Many of the crit path
features however affect a large or extremely large package set (e.g.
the sysv->systemd script migration), in which case explicitly
involving every maintainer as the feature owner before even proposing
the feature wouldn't scale; that's where FESCo does need to step in as
a more efficient way to represent the large group of packagers.
Case in point for F18 [1] and perfect example of one thing that should
have been completed within one release cycle...
JBG
1.http://fedoraproject.org/wiki/Features/PackagePresets