Test Update Tracking proposal

[Warren Togami]

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=114986
This is the first test of the "Tracking" report concept, where users 
report only definite findings for Fedora Test Updates while discussion 
remains on the mailing lists.  This helps to organize information about 
the update away from the chaos of the mailing lists so it is easy to find.

I also envision this as being a method of fostering multiple 
communities/lists to get involved.  In the case of gdm above, the 
K12LTSP community is very much involved with production testing along 
with the regular fedora-test-list.  In other cases we may have upstream 
project lists involved in testing.  This may also get the attention of 
upstream developers who are more likely to see the discussions.  Fedora 
has a chance to remain better in sync with upstream with improved 
communication, rather than Fedora-specific patches sit in our SRPM for 
years.  While discussions may be scattered on multiple lists, definite 
findings are sent to these tracking reports at Fedora.

The best part of what these tracking reports is something like this:
http://www.fedora.us/NEEDSWORK
http://www.fedora.us/PUBLISH
http://www.fedora.us/LEGACY

At any time, a site visitor can quickly use pre-set queries like these 
and immediately see the status of all Test Updates.  If they run into a 
bug, they can quickly see if the package is already fixed and only 
needing functionality testing.  All without sifting through the heavy 
traffic of mailing lists.  One thing that would need to be enforced for 
this to work is strong discouragement of discussion within the Tracking 
reports.  Only definite findings should be posted within there. 
Discussions on lists only.

For this easy-and-quick query ability, we could use the Developer 
Whiteboard, but I am requesting a permanent keyword like "UPDATE".  The 
pre-set query can search for "Fedora Core", "1", and keyword "UPDATE" 
and display everything.

Thoughts?

Warren Togami
wtogami at redhat.com