Fedora 13 Release Candidate Phase

John Poelstra poelstra at redhat.com
Thu May 13 13:22:02 UTC 2010

Jesse Keating said the following on 05/12/2010 03:11 PM Pacific Time:
> On Thu, 2010-05-13 at 02:42 +0530, Rahul Sundaram wrote:
>> On 05/13/2010 02:37 AM, Bill Nottingham wrote:
>>> There was an open ticket requesting Pino. There was not anything from
>>> the maintainers requesting the games.
>> I did mention this on IRC but what is the criteria for pulling in the
>> updates?  If I knew what would be reasonable to request, it would help
>> for future releases.  I am also looking for guidelines on, what updates
>> are considered a good thing.    Is the game update a problem?
>> Rahul
> I was trying to do away with the tickets for freeze exceptions, as I was
> trying to do away with freeze exceptions outside of blocker bugs.
> However there are a few bugs which we would classify as "not blockers"
> but things which we "would take a fix for".  These generally start out
> by being proposed blockers.

I'd like to see these "would take a fix for" bugs added or kept on the 
blocker list with a short comment explaining why they are being taken in 
since they don't meet the regular definition of "blocker bug".

This provides a very clear list of bugs that should get extra 
verification attention when the RC comes out.  It also provides a clear 
trail of the decisions made so others can understand our process and 

> The process isn't perfect, nor all that documented, as we're exploring
> as we go.  This is the first time we've done a RC phase with the no
> frozen rawhide style of development.  I suspect we'll be better about
> process and documentation next time around.

I'm looking forward to continuing to help expand the documentation about 
our release processes.  This is important because then everyone is 
working with the same information and can approach the process in the 
same way.


More information about the devel mailing list