On 08/03/13 04:19 AM, Kamil Paral wrote:
I never intended to say that the web app is necessary for the process to work. If it is down, all of my proposed work-flow can be done by hand. If it is not ready by Fedora 19, we don't have to use it at all. The bugzilla messages won't be so pretty and unified, but the core of the proposal was a different nomination process, not directly tied to the web app. If we change the SOP and the web app is not ready, it will not be so straightforward, but hey, that's it. The user can still contact the developer via bugzilla or IRC ask him to nominate the particular bug for a freeze exception. The developer can still tag the bug and provide justification in the comment. Just the crutches are not there. (By the way, the last few sentences was a TL;DR version of my whole proposal, minus the web app adjustments). Keep the critique coming :) I have a feeling that I haven't explained properly that the core of the proposal is a SOP change, and the web app workflow is just a bonus to make it prettier. Is it clearer now? Do you still have the same concerns?
To an extent, yeah. I guess I just feel like the 'manual' version of this process is too complex to rely on, and would result in bugs that should be nominated not getting nominated.
-- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
