As there were no new proposed bugs and many people were not available due to DevConf activities, the meeting was cancelled.
Minutes: https://meetbot.fedoraproject.org/teams/fedora_prioritized_bugs_and_issues/f...
On Wed, 2017-01-25 at 16:10 +0100, Jan Kurik wrote:
As there were no new proposed bugs and many people were not available due to DevConf activities, the meeting was cancelled.
Minutes: https://meetbot.fedoraproject.org/teams/fedora_prioritized_b ugs_and_issues/fedora_prioritized_bugs_and_issues.2017-01-25- 15.00.html
My apologies for not making the meeting. I had meant to ask about how to move a bug forward.
https://bugzilla.redhat.com/show_bug.cgi?id=1385432
Is there any information I can gather to assist in getting this bug looked at?
Thanks,
Charles
Hi Charles,
you can follow the https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_an... and nominate the bug for Evaluation on the next meeting (in two weeks). Basically, what you need to do is to set "PrioritizedBug" keyword into "Whiteboard" of the bug. You can join the meeting then to help us understand why it should be included on the prioritized list.
Regards, Jan
On Wed, Jan 25, 2017 at 5:09 PM, charles profitt fedora@cprofitt.com wrote:
On Wed, 2017-01-25 at 16:10 +0100, Jan Kurik wrote:
As there were no new proposed bugs and many people were not available due to DevConf activities, the meeting was cancelled.
Minutes: https://meetbot.fedoraproject.org/teams/fedora_prioritized_b ugs_and_issues/fedora_prioritized_bugs_and_issues.2017-01-25- 15.00.html
My apologies for not making the meeting. I had meant to ask about how to move a bug forward.
https://bugzilla.redhat.com/show_bug.cgi?id=1385432
Is there any information I can gather to assist in getting this bug looked at?
Thanks,
Charles _______________________________________________ triage mailing list -- triage@lists.fedoraproject.org To unsubscribe send an email to triage-leave@lists.fedoraproject.org
triage@lists.fedoraproject.org