Difference between revisions of "User:Grundleborg/BugsquadKMailWorkflowTest"

Jump to: navigation, search
(Workflow)
(Workflow)
 
Line 13: Line 13:
 
* Request more information if necessary - be specific, ie. don't just say "MORE INFORMATION NEEDED"...
 
* Request more information if necessary - be specific, ie. don't just say "MORE INFORMATION NEEDED"...
  
* If you can reproduce the bug as described, comment on the report saying that you can with the svn revision number you used to test and any additional information/instructions that might be useful to developers, CONFIRM the bug, and reassign it to the mailing list ''kdepim-bugs kde org''. Also, add the '''TRIAGED''' keyword. It will then be handled by the developers.
+
* If you can reproduce the bug as described, comment on the report saying that you can with the svn revision number you used to test and any additional information/instructions that might be useful to developers, CONFIRM the bug, and reassign it to the mailing list ''kdepim-bugs kde org''. Also, add the '''TRIAGED''' keyword. It will then be handled by the developers. Also try and make sure that it is assigned to the correct component of KMail, not just ''general''.
  
 
'''Please feel free to flesh out this page with more information that you think is relevant/helpful.'''
 
'''Please feel free to flesh out this page with more information that you think is relevant/helpful.'''

Latest revision as of 16:33, 17 October 2008

[edit] KMail Just In Time Bug Triage

This page describes the steps for dealing with the experimental new process for prescreening of KMail bugs.

In order to take part in this, you should be subscribed to the mailing list bugsquad-triage kde org.

[edit] Workflow

When a new bug is reported, it will initially be assigned to the bugsquad triage mailing list. If you see one of these new bugs, you should attempt to triage it. Try and reproduce it as the reporter describes using a recent KMail trunk version. Then take one of the following actions with it.

  • Close it as WORKSFORME/INVALID/DUPLICATE where appropriate (remembering to leave a comment how you tested this bug report).
  • Request more information if necessary - be specific, ie. don't just say "MORE INFORMATION NEEDED"...
  • If you can reproduce the bug as described, comment on the report saying that you can with the svn revision number you used to test and any additional information/instructions that might be useful to developers, CONFIRM the bug, and reassign it to the mailing list kdepim-bugs kde org. Also, add the TRIAGED keyword. It will then be handled by the developers. Also try and make sure that it is assigned to the correct component of KMail, not just general.

Please feel free to flesh out this page with more information that you think is relevant/helpful.


This page was last modified on 17 October 2008, at 16:33. This page has been accessed 1,046 times. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal