I don't think there's any hard fast rule. Generally, unless you know beyond a doubt that it's a bug (and you generally have a patch for it at that point), I'd recommend bringing it up on the user or dev list as appropriate and see if anyone has a comment first.
Because this is open souce, opening a JIRA issue typically is most helpful if you're planning on resolving it at some point -- there's no "paid help" who are going to drop what they're doing and fix something for you. It can also be helpful for documenting problems that may be beyond your ability to fix just so that others are aware of the issue. On 8/1/06, Joseph Rozier <[EMAIL PROTECTED]> wrote:
I saw Matthias' comment on ADFFACES-104 regarding the protocol for bringing up issues on the adffaces-dev list vs. opening a JIRA. https://issues.apache.org/jira/browse/ADFFACES-104#action_12424717 Am I correct in assuming this is the preferred protocol: 1) if it is an obvious bug (e.g. a NullPointerException is being thrown, etc.), open a JIRA 2) if it is a new feature, e-mail -dev; after discussion, open a JIRA Is #1 a valid case, or should we ALWAYS e-mail adffaces-dev before opening a JIRA? For #2, at what point is the decision made to open a JIRA? Do we need go ahead from a commiter? Also, it seems there is a category #3: it seems like a bug, but maybe it's not? In ADFFACES-104 for example, when I first read the issue I assumed it was a bug that had slipped through Matthias' amazing refactoring work. I could have seen myself filing a JIRA under case #1 above thinking that this was an "obvious" bug. (I suppose the idea here is--before assuming a change someone else did/didn't make is a bug, e-mail adffaces-dev.) Once the protocol is clarified, I'd also like to add this to the "involved" wiki... http://wiki.apache.org/myfaces/ADF_Faces/involved Thanks, Joey
