(→Previous Bug Days) |
(→Previous Krush Days) |
||
| Line 42: | Line 42: | ||
A Krush day is where the Bugsquad tests the target application and reports all the bugs they can find in it. | A Krush day is where the Bugsquad tests the target application and reports all the bugs they can find in it. | ||
| + | * [[/KOfficeDay2|KOffice Bug Day 2: Sunday, Januar 25th 2009]] KOffice Krush (IN preparation for 2.0 release) | ||
* [[/KOfficeDay1/Krush|KOffice Bug Day 1, krush: Sunday, October 26th 2008]] KOffice Krush (In preparation for 2.0 release) | * [[/KOfficeDay1/Krush|KOffice Bug Day 1, krush: Sunday, October 26th 2008]] KOffice Krush (In preparation for 2.0 release) | ||
* [[/KDEPIMKrush1|KDE PIM Krush Day 2: Sunday, June 8th 2008]] KDE PIM Krush (In preparation for 4.1 release) (Continuation from previous KDE PIM Krush Day 1 on the same page). | * [[/KDEPIMKrush1|KDE PIM Krush Day 2: Sunday, June 8th 2008]] KDE PIM Krush (In preparation for 4.1 release) (Continuation from previous KDE PIM Krush Day 1 on the same page). | ||
This page contains links to the pages for all past bug triage events.
Contents |
The next Bug Day will be 10th October 2010 and it will the first KWin Bug Day: http://techbase.kde.org/Contribute/Bugsquad/BugDays/KWinDay1
A Bug Day is where the Bugsquad goes back through bugs in bugzilla for a particular application and closes all reports that are no longer valid.
A Krush day is where the Bugsquad tests the target application and reports all the bugs they can find in it.
Prior to the convening of the Bugsquad in its current form, there were a number of Bug Triage and Krush events. Tehcbase pages used for these events can be found below.
KDE TechBase 