(from a barely edited irc log, with nixeagle's permission)
The first three mostly apply to Konqueror & rendering bugs:
If it has a testcase, toss it into the "testcase section" of the wiki. If it is a fixed bug, put it under the "fixed" section, AND mention that it has a testcase. This way all the testcases can be added to the test regression suite.
|Old konqueror bugs aren't likely to have duplicates. Always get a second opinion, traditionally dups are the highest false positives, and we do not want to close valid, real bugs. Our first time, we ended up with only 3 duplicates, out of 355 bugs. This probably won't apply with fresh, incoming bugs. But don't worry about dups if you are new.|
All the incoming flash bugs are probably dups. :P They are most useful if they are reproducible and have good instructions on how to reproduce. Also the reporter should give: flash version, kde version, 32/64bit. I'm told the backtraces don't matter as much as the reproducibility.
See the flash wikipage: http://techbase.kde.org/index.php?title=Contribute/Bugsquad/BugDays/flashplugin (checklink)
See if it has a testcase, see if you can write one, put it on the wiki. Add a note saying the bug is still present and agian, and don't forget to give what version you're using.
It gives us an easy way to go through and double check what people have done, especially useful for those who don't have bugzilla perms.
But you also have to mark things on bugzilla, that's where developers will keep track of things. We use the wiki to coordinate our own efforts.
Depends on what section If you go up a level or so from the link in the topic, you'll find the one from the last time we did this
You'll see how it's ended up looking now that we've gone through it a few times We're not putting any new bugs on there.
|If you just got a techbase wiki account, set the preferences to let you edit by section.|
We also use the wiki to some extent to coordinate comments, at least to document what we said in irc.
We want to keep it all on one page, because on the 2nd and 3rd pass, we tend to move things around a LOT from section to section as stuff changes.
A ton. You can check at http://bugs.kde.org/weekly-bug-summary.cgi You can also click through to your favorite application and see its components' bugs. They will be sorted by severity here, so this is one way to go look at a list of crashes or wishlists. If you look at the past, you will find that ever since BugSquad has started, we have been making KDE "green".