openerp-community-committers team mailing list archive

[Jan Verlaan - Veritos <jverlaan@xxxxxxxxxx>]

Hi Albert,

if user files a bug at our project a messages appears with explanation
You may try at https://bugs.launchpad.net/community-addons/+filebug

Of cause this message can be edited to what we agree upon. It should 
make the user clear if this is the right place or that the bug should be 
reported add openerpsa bugtracker.

A copy of the message:


     Community Openobject Addons bug reporting guidelines:

IMPORTANT:
Reporting a bug should be done at 
https://bugs.launchpad.net/openobject-addons 
<https://bugs.launchpad.net/openobject-addons> where OpenERP SA does 
their bugtracking for the addons modules.

This bugreport facility is only for the extended community version if 
you are sure a bug is NOT caused by the standard version and for re- and 
co-assigning bugs from standard to this project.

If you sure that you want to report a bug in this project, you are 
requested to use the following template to give your bug information. 
This will secure the needed information to understand the problem by a 
developer.

SITUATION IDENTIFIED IN:

REPRODUCTION ENVIRONMENT:

PROBLEM DESCRIPTION:

SPECIFIC PARAMETER SETUP:

STEPS TO BE FOLLOWED:

OBSERVED RESULT:

EXPECTED RESULT:

ADDITIONAL COMMENTS:




Op 18-11-10 23:27, Albert Cervera i Areny schreef:
> How will end users decide the appropriate project to report the bug report to?
> What if we use a couple of tags in existing bug reports: "fixedincommunity" and
> "communityonly". That way, OpenERP sa can easily search all bug reports that
> have been fixed in our branch.