Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 292693

Summary: Update "How to post a RAP bug"
Product: [RT] RAP Reporter: Holger Staudacher <holger.staudacher>
Component: WebsiteAssignee: Project Inbox <rap-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Holger Staudacher CLA 2009-10-19 14:09:27 EDT 
Today I talked to Moritz Post about posting RAP bugs. He followed the steps on http://wiki.eclipse.org/RAP_Bug_Reporting_Howto to make all as clear as possible (nice work). I ask him if it's possible to prefix the design bugs with [design] and he accepted. Additional he mentioned that this "prefixing" should also be a part of the "bug tutorial". So, I think it would be nice to add the categories to the tutorial, what did the rest of the RAP team think?
Comment 1 Benjamin Muskalla CLA 2009-11-03 18:33:48 EST 
JDT does something similiar (see http://eclipse.org/jdt/ui/doc/bug-annotation.php) but I think this should be part of the triage process. There are many cases that a bug I filed with a specific usecase in mind (eg. Bug in Tree) but in reality the bug belongs to another categorie (eg. [releng] because images are missing).
In my eyes the prefixing should be done by us during the triage process.
Comment 2 Rüdiger Herrmann CLA 2009-11-05 07:21:50 EST 
I agree with Benny. Prefixing is part of the bug processing. The bug summary often also needs other adjustments, so the extra effort of tagging it with a prefix can almost be neglected.
Moreover it would only help if everyone would read and adhere to the how-to;)