I think in a previous thread we identified some issues, and some possible solutions. I think to help assure the quality of our distro we need to create a QA team, with a good structure. One of the issues will be having strong centralized communication. I believe I can provide an excellent tool for this, as long as nobody is opposed to using an outside tool. 1. Establish QA team and resources 2. Divide the team into units 1. Assign area heads based on speciality. 2. Divide KDE testing into logical blocks of applications, such as plasma team, PIM team, etc. 3. Establish triaging guidelines and methodology. 1. Looks like the wiki has good guidelines on this 2. Check and compile lists from Bugzilla to create test cases 4. Efficient testing 1. Assign testing tasks and blocks to team members (self assigned or team sublead assigned is fine) 2. Track tasks, and keep notes. 1. The tool I have in mind and have access to is supremely suited to this. 5. Report findings 1. File new bug reports in the case of a bug being SOLVED, and flag the old possibly associated bugs with the new report. Check upstream for related reports. 2. Compile task list of outstanding bug findings, and check with upstream to see if problem is known or patched. 1. If the bug is unknown, file a new report with KDE 2. If the bug is patched, add to list of fixes that need to be applied. I think that about covers it. Queue brainstorm! -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org