Based on the announcements to the list, I have updated https://fedoraproject.org/wiki/BugZappers/How_to_Triage#How_to_Mark_as_Triaged to the below text. Just wanted to make sure this is accurate and desirable. -B. --- How to Mark as Triaged If you have completed the entire checklist for a bug, you should mark it as triaged so that others will not duplicate your efforts. For Fedora 12: * If the bug now has all the information the maintainer needs, mark it as ASSIGNED. If you are waiting on information from the reporter, leave it as NEW and check the "Need information from" box and set the pulldown appropriately. * Either way, add "Triaged" to the Keywords field. For Rawhide, Fedora 13, and later releases: * Add "Triaged" to the Keywords field. Do not change the bug's status. If information is missing from the report, check the "Need information from" box and set the pulldown appropriately. Closing Bugs Many bugs are fixed upstream or unintentionally during a seemingly unrelated rewrite. If someone who has experienced the bug can confirm that is is fixed by an update to the version of Fedora is it reported against, mark it CLOSED/ERRATA. Normally when a package maintainer intentionally fixes a bug, this is recorded in the build system, and Bodhi should automatically close the bug when the update goes live. (But this does not happen for Rawhide bugs.) -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
