So now we're past Beta, I see this kind of thing popping up again: https://bugzilla.redhat.com/show_bug.cgi?id=959677#c35 "Nice! If anybody wants a patch for this to be included in the final release, please propose this as a final blocker." Please don't abuse the project-wide blocker process in this way. The blocker process is for tracking bugs that must be fixed before the release. It is not a todo list or a private freeze exception list. The official freeze date for F19 Final is 2013-06-18, it is listed as "Final Change Deadline" at http://fedorapeople.org/groups/schedule/f-19/f-19-devel-tasks.html . So far as the Fedora project is concerned, there is no freeze until that time. If the anaconda team wants to apply a private freeze to anaconda changes for the entire post-Beta period it is your right to do so, however, you should either come up with your own mechanism for tracking exceptions to your private freeze or at least work with other teams to decide how existing mechanisms can sensibly be applied to your private freeze, not simply decide to start using the project-wide release blocker tracking mechanism as a private freeze break list. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
