(You can do this anytime, picking a day just helps us focus. It's how we do our basic training.)
Also, if you are new, this is where we will keep track of how you are doing.
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.
If you can't make a testcase, note "testcase needed" in the wiki.
Also, try http://archive.org and see if you can pull up the site from around that time. Paste that link in the report, or better yet, make a testcase and put that in.
(Or you can close with INVALID or WONTFIX, depending on what it is. Different programs/developers have different styles, i.e. REMIND vs. WONTFIX/INVALID. If you find yourself triaging for one package, you might want to find out the maintainer's style and follow that.)
|Old Konqueror bugs aren't likely to have duplicates. Always get a second opinion on those, traditionally duplicates are the highest false positives in BugDays, and we do NOT want to close valid, real bugs. In old Konqueror bugs, we've found about 1% duplicates. (This isn't the case with incoming bugs.) So don't worry about finding duplicates if you are new.|
Many of the incoming flash bugs are duplicates. They are most useful if they are reproducible and have good instructions on how to reproduce them, or a URL. Also the reporter should give: flash version, kde version, 32/64bit. The backtraces will be incomplete inside of the flash functions: there are no debug symbols for it (closed source). Backtraces are still useful if flash is causing a crash though, because it helps us figure out how to work around it or tell if they have something misconfigured.
See the flash wikipage: http://techbase.kde.org/index.php?title=Contribute/Bugsquad/BugDays/flashplugin
It would be nice if you go through and comment on these test cases, you don't even need a bugzilla or techbase account.
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 again, don't forget to give what version you're using.
3.5.x is not in active development at this time. Technically speaking, it's seven+ releases out of date. True, 4.1.x doesn't have all the functionality of 3 yet, but 3.5.x is past string freeze, feature freeze, etc. Keep that in mind as you go through old reports. You can use this to justify closing items fixed in trunk, while being nice to reporters who say they can't upgrade.
(Bugzilla actually has states (resolved -> verified -> closed) to keep track of code shipping, etc., but it's just a waste of time for us, so we don't use it that way.)
Normally bug reports are fixed in the current development version (trunk), and "safe" bugfixes are backported to the current stable version (4.0 branch). Older versions just get security fixes. If something got messed up only on the stable branch, it gets fixed there.
The point of bugzilla is to keep track of what needs fixing in versions currently being worked on.
Once a bug is fixed in SVN trunk, it can be closed.
Shall I say it again? This is true for 4.1 vs. SVN trunk too!
This won't necessarily make users happy, so be nice about closing old bugs. Here are some further guidelines:
They are not actively developing 3.5.x Crashes: If it happens on cnn.com or some such important site, it might get backported, otherwise, they're not going to be touched. Ask channel how important they think it is, and then go bug a developer to backport.
If konqueror crashes when restoring session, please zip the $KDEHOME/share/apps/konqueror/autosaved directory and attach it to the bug report. This way the developers will be able to restore the problematic konqueror session exactly as you do, and it will be easier to fix the problem.
There was major code change between 3 & 4. Any kind of backport is probably undoable.
SKIP these bugs There is ongoing major code change. They won't change 1.6 bugs, but 2.0 is still alpha. The developers want to keep their bugs open to check for regressions later on.
If you see someone saying their bug shouldn't be closed until everyone (read: that person) could give up kde3, try to come up with something nice to say, but really what they think is irrelevant. This is a case where we can take the heat for developers. We don't want them to have to deal with this stuff.
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: Perhaps you'd like to see previous examples?
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".
Thanks to nixeagle, who let me start this page from an unedited irc log. Also thanks to others who probably don't want to be mentioned.