This "users" list is the appropriate place to raise initial questions about issues which might be bugs. Once the issue is confirmed on the list to be a bug it's a good idea to create a JIRA so it doesn't get lost in the shuffle.
Regarding the VOTE process, that's a standard Apache practice when new releases are proposed. However, in ActiveMQ this is (usually) done on the "developer" list [1]. If you're interested in participating in this process (e.g. if you have a specific issue you're concerned about) then I recommend you subscribe to that list. Here's the VOTE email [2] I sent about the 2.4.0 release. In general the best way to ensure an issue you care about gets fixed is to submit a fix for review (typically done via a pull-request on GitHub). If the fix is good it will be merged into the code-base. Justin [1] http://activemq.apache.org/mailing-lists.html [2] http://mail-archives.apache.org/mod_mbox/activemq-dev/201711.mbox/browser On Mon, Nov 13, 2017 at 12:22 PM, hcrobison <hrobi...@industrialdefender.com > wrote: > Thanks but these all sound pretty foreign to me. > First, are you saying, as a user, we should create a JIRA when we find a > bug? > Second, what is this VOTE process you are speaking of? > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
