Hi folks,

some minutes ago the following ticket has been opened:

https://issues.apache.org/jira/browse/LOGCXX-437

To me this reads like something which should have been discussed
before opening a ticket on the user mailing list, because I doubt it's
a bug in Log4cxx, but a a problem with the user specific build process
or such. In any case, form my point of view it's simply to unspecific
to work as a bug, the user needs to provide more details to help him
and I don't think such common things are well suited in JIRA.

So I would propose to advice people with common "things don't
work"-issues to the users mailing list first and decide there if
something is a bug or not and create a bug in JRA afterwards.

The problem now is that we have the following sentence:

> Issues, bugs, and feature requests should be submitted to the
> following issue tracking system for this project.

But we don't want "issues" in JIRA, issues belong to the users mailing
list. I would change that template to provide a more detailed
explanation of what we want in JIRA and what should be posted to the
users mailing list first.

Any objections?

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Reply via email to