[Fedora-spins] Fedora 10 Beta Freeze (Spins)

Bryan Kearney bkearney at redhat.com
Wed Sep 17 12:50:02 UTC 2008

John Poelstra wrote:
> Jesse Keating said the following on 09/16/2008 08:32 AM Pacific Time:
>> On Tue, 2008-09-16 at 09:45 +0200, Jeroen van Meeuwen wrote:
>>> Yes it sounds like we need to. I'm taking the categories as an indicator 
>>> now, but maybe that's not what you use and flip when a spin is accepted 
>>> or not.
>> Well, this process is still a bit... new, so I'm not surprised there is
>> some rough road.  I think we (rel-eng) has been expecting John Poelstra
>> to bring these spins for approval to our attention, just as he brings
>> features to FESCo's attention.  I'm not sure /he/ was expecting that
>> though, so it would not be surprising that some things haven't bee
>> communicated.
> Yes I was not clear on exactly what the process is and still am not.
> I apologize for the confusion I created by changing the category to 
> FeatureAcceptedF10.
> I changed a couple of them and then stopped when I realized that it 
> didn't make complete sense as the "feature process" I help manage 
> relates specifically to features approved by FESCo.  Those features are 
> listed here: https://fedoraproject.org/wiki/Releases/10/FeatureList.
> I asked a few people what the process around spins was supposed to be, 
> but couldn't get any clear answers.  I should have posted to 
> fedora-devel list and sought clarification.  It seemed odd to me that 
> all our documentation describes how FESCo "accepts" features that are 
> listed here https://fedoraproject.org/wiki/Releases/10/FeatureList and 
> then to start adding Spins to the same page which go through a similar, 
> but more different process that aren't exactly "accepted" by FESCo, as I 
> understand it.  Forgive me if I've made this too complicated :)
> I see two processes going on here which I perceive as follows:
> 1) "FESCo feature" process
> --clearly documented here what happens when and by who: 
> https://fedoraproject.org/wiki/Features/Policy/Process
> 2) Spins process
> --No process flow that I have found defined that I can figure out 
> exactly which part I am supposed to be helping with nor is it clearly 
> defined how the approval/acceptance process is tracked and where they 
> end up or are listed once said approval/acceptance/rejection has taken 
> place.
> At present I can't commit the time to manage or define the process 
> around spins approval/acceptance, but could help with drawing a 
> flowchart if that helps clarify things.

Does this help?


-- bk

More information about the rel-eng mailing list