The 4.6-beta1 BugWeek will be from 11.12 till 17.12 :)
This bugweek tries to improve the quality of the 4.6 release by triaging all recent bug reports (bugs from 4.6-beta1 and the pre-beta versions). We also check if the bugs for 4.5 apply for 4.6 and triage those.
You should have a recent version of KDE, preferably trunk or the beta 1 release. You can still help if you only have the 4.5.3 release though.
Some packagers provide LiveCD/DVDs to faciliate testing:
For some distributions pre-compiled and -packaged versions of trunk or the beta are available in additional repositories, ready for consumption:
Prioritizing is good. If a major application doesn't work, this should be taken care of.
After adding triaged bugs on this page, you should keep an eye on their bugzilla status. Add yourself on the CC field in bugzilla to be informed about updates. When a bug is closed on bugzilla, it should be updated on this page.
You can do this with the tag <s>...</s>
Tell developers what you are testing with. (If you expect to upgrade between now and BugDay, put what version you are using now next to the bugs/comments that you put on this page.)
Please give distro/version or SVN branch/trunk with revision below (or just beta1 if you're using that). It would be helpful to add what distribution you use.
|IRC Nickname||KDE version used for testing||Distribution|
Please select a batch of bugs from the Division of Labour section below and mark your name next to it and mark it with your irc nickname to show that you are working on it. When you have completed all the bugs in that section, please mark it as complete.
For each bug, try and reproduce it as described in the report. Then list it in the appropriate section below. If you wish to close or mark as duplicate a bug, please list it here even if you have the bugzilla permissions to do so, in order to get a second opinion from another triager. This will help to reduce the number of incorrect actions taken on bugs.
Please choose a batch that is not already taken and then query bugs.kde.org for all bugs in that batch. Please mark you irc nickname in the table below to show which batches bugs you are working on to avoid duplication of effort.
|Batch||No of bugs||IRC Nickname||Status||Query|
(total bugs: 199)
Below lists the various sections for completed bugs. This aids everyone in double checking each other's work. In addition this allows those of us that don't have bugzilla permissions to list bugs so that the folks with the permissions can follow up.
Please note that this is an experimental layout designed to reduce the number of edit conflicts on this page. Each section is its own subpage. The best way to work with this is to enable section editing by going to "My preferences" > "editing" > "Enable section editing via  links". When you click edit you will automatically edit the subpage.
Some bugs are more important than others, eg.
If you think a bug is of high priority and needs to be fixed as soon as possible, put it here.
If you don't have bugzilla permissions yet, you can't change version fields. Put what needs changing here and someone else will go through and do it for you.
If it is a deterministic bug, put it here. Make sure it has instructions. You should be able to verify it. (Write that you did on bugzilla and include your version information.)
If the bug doesn't exist anymore, it goes here. WORKSFORME!
Put suspected duplicates here.
A bug is INVALID if it describes desired behavior, or something that isn't a bug.
If a bug was previously UNCONFIRMED and you can reproduce it, put it here.
If anything is in doubt, put it here, and give a description of why you think a developer should look at it.
If a bug sounds valid but can't really be reproduced and needs more information from the reporter, put it here.
If a bug needs for example special hardware or a specific video driver or other particular configuration, put it here.
Put here bug reports against performance issues.
If there are bugs you can't test for whatever reason (apart from the ones needing a particular setup which have their own section), fill those in here.
If the bug should actually be a wish and needs to be marked as such, put it here.