Feature template update [was Re: Anaconda is totally trashing the F18 schedule...]

drago01 drago01 at gmail.com
Thu Nov 1 18:50:26 UTC 2012


On Thu, Nov 1, 2012 at 7:45 PM, Jaroslav Reznik <jreznik at redhat.com> wrote:
> ----- Original Message -----
>> On Thu, Nov 1, 2012 at 7:34 PM, Matthew Miller
>> <mattdm at fedoraproject.org> wrote:
>> > On Thu, Nov 01, 2012 at 02:09:21PM -0400, Jaroslav Reznik wrote:
>> >> > That sounds good. Maybe recast those ideas as three levels?
>> >> >  - Critical Path Feature
>> >> >  - Other Enhancement Feature
>> >> >  - New Leaf Feature
>> >> We were thinking with a few folks more about "Self contained
>> >> feature"
>> >> but yeah, there's a lack of real definition.
>> >
>> > I think "Leaf" is better than "Self contained", since it's unlikely
>> > for the
>> > feature to have zero outside dependencies. I think it'd be fine for
>> > such a
>> > feature to rely on small changes to existing packages (version
>> > updates,
>> > say).
>>
>> I'd argue that this isn't a "feature" ... otherwise we could
>> advertise
>> every version upgrade as feature.
>> If it does not affect a large amount of users it is simply a version
>> upgrade not a "fedora feature".
>
> The question is - how do you know if it affects large amount of users,
> it's not an important one, without letting people know, there's such
> feature?

Does a lot of other packages depend on it? -> Likely affects a lot of users.
Is it installed by default or a commonly used application / package ?
-> Likely affects a lot of users.
Is it a new package that isn't intended to be installed by default? ->
Probably does not affects a lot of users.
... etc.

So while there is no 100% accurate definition applying some common
sense helps here.


More information about the devel mailing list