Release criteria updates: genericizing!

[Clyde E. Kunkel]

On 06/23/2011 10:46 AM, James Laska wrote:
> Greetings testers,
>
> I've been playing with some ideas on how to allow secondary
> architectures to leverage the primary release criteria.  I have some
> ideas/challenges that I'll send to the list for feedback later.
> However, in preparation for those ideas/concerns, I'd like to propose
> several changes to the release criteria.
>
> The proposed changes are intended to make the existing criteria slightly
> more generic, without losing their meaning.  Additionally, I've made a
> few other minor changes and added a few questions.  Please take a few
> minutes to review the proposed changes (highlighted in red at the links
> below).  If nothing alarming surfaces during review, I'll proceed with
> operation genericize [1] early next week.
>
> https://fedoraproject.org/wiki/User:Jlaska/Draft_Alpha_criteria_revision
> https://fedoraproject.org/wiki/User:Jlaska/Draft_Beta_criteria_revision
> https://fedoraproject.org/wiki/User:Jlaska/Draft_Final_criteria_revision
>
> Thanks,
> James
>
> [1] Kudos to Adam for coining this gem!
>

What should be done with nth bzs that were not resolved before 15 went 
to press and have not been resolved with an update and are now present 
in rawhide?  Should they be moved up in priority and/or automatically 
added to the 16 blocker bz?

An example: https://bugzilla.redhat.com/show_bug.cgi?id=681582

(BTW: 681582 probably should have been in the 15 release notes.)


-- 
Regards,
OldFart