Grundleborg (Talk | contribs) (→Previous Krush Days) |
Grundleborg (Talk | contribs) (→Previous Krush Days) |
||
| Line 17: | Line 17: | ||
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. | ||
| − | * [[/KDEPIMKrush1|KDE PIM | + | * [[/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 | + | * [[/KDEPIMKrush1|KDE PIM Krush Day 1: Sunday, May 25th 2008]] KDE PIM Krush (In preparation for 4.1 release). |
==Previous bug triage events== | ==Previous bug triage events== | ||
* [[Contribute/Bugsquad/KrushDays|KDE4 Krush Days]] | * [[Contribute/Bugsquad/KrushDays|KDE4 Krush Days]] | ||
* [[Contribute/Bugsquad/Bug_weekends|Konqueror Bug Weekends]] | * [[Contribute/Bugsquad/Bug_weekends|Konqueror Bug Weekends]] | ||
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.