You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2026/02/19 16:41:46 UTC
GitHub Issues & Discussions enabled
Hi folks,
We are pleased to announce that GitHub Issues & Discussions.
1. GitHub Issues (https://github.com/apache/activemq/issues)
Jira is now read-only and we should now all use GitHub Issues.
We have the following labels available:
- bug: for bug reports
- dependencies: for dependencies updates
- enhancement: for improvements on existing code
- feature: for a complete new features
- proposal: for a design proposal, big features
- stale: when the issue is "inactive" for more than 60 days
Please use these labels to classify the issues.
When you create a PR, you can associate it with an issue either in the
GitHub UI or using "This closes #xxxx" in the comments.
I also suggest using conventional commit messages in PR with the
format <type>(<scope>): <subject> where scope is optional. The type can be:
- feat: (a new feature is introduced with the changes)
- fix: (bug fix has occurred, not a fix to a build script)
- docs: (changes to the documentation)
- style: (formatting, missing semicolons, etc; no production code change)
- refactor: (refactoring production code, eg. renaming a variable)
- test: (adding missing tests, refactoring tests; no production code change)
- chore: (changes that do not relate to a fix or feature and don't modify
src or test files (for example updating dependencies or change in
production code))
- perf – (performance improvements)
- ci – (continuous integration related)
- build – (changes that affect the build system or external dependencies)
- revert – (reverts a previous commit)
That's a nice practice because GitHub can use that to create nice Release
Notes.
Thanks to that, it's not necessary to create GH issues for all changes.
For versions, we are using GitHub Projects (
https://github.com/apache/activemq/projects?query=is%3Aopen).
You can assign several projects/versions per issue, and track the status of
the versions.
2. GitHub Discussions
We also enabled GitHub Discussions where we can have technical discussions.
The GH Discussions are automatically going to the dev@ mailing list.
Let us know if you have any questions.
Regards
JB
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Please let me know if you need any help here.
On Thu, Feb 19, 2026 at 11:20 PM Havret <ha...@apache.org> wrote:
> If it’s up to me, I’m definitely in favor of switching to GitHub Issues.
>
> KP
>
> On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> dev@activemq.apache.org> wrote:
>
> > Nice!
> >
> > Will all old Jira issues be migrated to GitHub too?
> >
> > Also, I'm wondering, how "stale" issues will be managed? I would hate to
> > see those bots automatically closing issues if they are "inactive". I
> > understand that sometimes there is a need to manage a backlog, but this
> > doesn't allow "voting" on issues with likes or other means of activity
> > other than "me too, please reopen" comments.
> >
> > --
> > Best Regards,
> > Vilius
> >
> > -----Original Message-----
> > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > Sent: Thursday, February 19, 2026 6:42 PM
> > To: dev@activemq.apache.org; users@activemq.apache.org
> > Subject: GitHub Issues & Discussions enabled
> >
> > Hi folks,
> >
> > We are pleased to announce that GitHub Issues & Discussions.
> >
> > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > Jira is now read-only and we should now all use GitHub Issues.
> >
> > We have the following labels available:
> > - bug: for bug reports
> > - dependencies: for dependencies updates
> > - enhancement: for improvements on existing code
> > - feature: for a complete new features
> > - proposal: for a design proposal, big features
> > - stale: when the issue is "inactive" for more than 60 days
> >
> > Please use these labels to classify the issues.
> >
> > When you create a PR, you can associate it with an issue either in the
> > GitHub UI or using "This closes #xxxx" in the comments.
> > I also suggest using conventional commit messages in PR with the format
> > <type>(<scope>): <subject> where scope is optional. The type can be:
> > - feat: (a new feature is introduced with the changes)
> > - fix: (bug fix has occurred, not a fix to a build script)
> > - docs: (changes to the documentation)
> > - style: (formatting, missing semicolons, etc; no production code change)
> > - refactor: (refactoring production code, eg. renaming a variable)
> > - test: (adding missing tests, refactoring tests; no production code
> > change)
> > - chore: (changes that do not relate to a fix or feature and don't modify
> > src or test files (for example updating dependencies or change in
> > production code))
> > - perf – (performance improvements)
> > - ci – (continuous integration related)
> > - build – (changes that affect the build system or external dependencies)
> > - revert – (reverts a previous commit)
> > That's a nice practice because GitHub can use that to create nice Release
> > Notes.
> > Thanks to that, it's not necessary to create GH issues for all changes.
> >
> > For versions, we are using GitHub Projects (
> > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > You can assign several projects/versions per issue, and track the status
> > of the versions.
> >
> > 2. GitHub Discussions
> > We also enabled GitHub Discussions where we can have technical
> discussions.
> > The GH Discussions are automatically going to the dev@ mailing list.
> >
> > Let us know if you have any questions.
> >
> > Regards
> > JB
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Please let me know if you need any help here.
On Thu, Feb 19, 2026 at 11:20 PM Havret <ha...@apache.org> wrote:
> If it’s up to me, I’m definitely in favor of switching to GitHub Issues.
>
> KP
>
> On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> dev@activemq.apache.org> wrote:
>
> > Nice!
> >
> > Will all old Jira issues be migrated to GitHub too?
> >
> > Also, I'm wondering, how "stale" issues will be managed? I would hate to
> > see those bots automatically closing issues if they are "inactive". I
> > understand that sometimes there is a need to manage a backlog, but this
> > doesn't allow "voting" on issues with likes or other means of activity
> > other than "me too, please reopen" comments.
> >
> > --
> > Best Regards,
> > Vilius
> >
> > -----Original Message-----
> > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > Sent: Thursday, February 19, 2026 6:42 PM
> > To: dev@activemq.apache.org; users@activemq.apache.org
> > Subject: GitHub Issues & Discussions enabled
> >
> > Hi folks,
> >
> > We are pleased to announce that GitHub Issues & Discussions.
> >
> > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > Jira is now read-only and we should now all use GitHub Issues.
> >
> > We have the following labels available:
> > - bug: for bug reports
> > - dependencies: for dependencies updates
> > - enhancement: for improvements on existing code
> > - feature: for a complete new features
> > - proposal: for a design proposal, big features
> > - stale: when the issue is "inactive" for more than 60 days
> >
> > Please use these labels to classify the issues.
> >
> > When you create a PR, you can associate it with an issue either in the
> > GitHub UI or using "This closes #xxxx" in the comments.
> > I also suggest using conventional commit messages in PR with the format
> > <type>(<scope>): <subject> where scope is optional. The type can be:
> > - feat: (a new feature is introduced with the changes)
> > - fix: (bug fix has occurred, not a fix to a build script)
> > - docs: (changes to the documentation)
> > - style: (formatting, missing semicolons, etc; no production code change)
> > - refactor: (refactoring production code, eg. renaming a variable)
> > - test: (adding missing tests, refactoring tests; no production code
> > change)
> > - chore: (changes that do not relate to a fix or feature and don't modify
> > src or test files (for example updating dependencies or change in
> > production code))
> > - perf – (performance improvements)
> > - ci – (continuous integration related)
> > - build – (changes that affect the build system or external dependencies)
> > - revert – (reverts a previous commit)
> > That's a nice practice because GitHub can use that to create nice Release
> > Notes.
> > Thanks to that, it's not necessary to create GH issues for all changes.
> >
> > For versions, we are using GitHub Projects (
> > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > You can assign several projects/versions per issue, and track the status
> > of the versions.
> >
> > 2. GitHub Discussions
> > We also enabled GitHub Discussions where we can have technical
> discussions.
> > The GH Discussions are automatically going to the dev@ mailing list.
> >
> > Let us know if you have any questions.
> >
> > Regards
> > JB
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
If it’s up to me, I’m definitely in favor of switching to GitHub Issues.
KP
On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
dev@activemq.apache.org> wrote:
> Nice!
>
> Will all old Jira issues be migrated to GitHub too?
>
> Also, I'm wondering, how "stale" issues will be managed? I would hate to
> see those bots automatically closing issues if they are "inactive". I
> understand that sometimes there is a need to manage a backlog, but this
> doesn't allow "voting" on issues with likes or other means of activity
> other than "me too, please reopen" comments.
>
> --
> Best Regards,
> Vilius
>
> -----Original Message-----
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Thursday, February 19, 2026 6:42 PM
> To: dev@activemq.apache.org; users@activemq.apache.org
> Subject: GitHub Issues & Discussions enabled
>
> Hi folks,
>
> We are pleased to announce that GitHub Issues & Discussions.
>
> 1. GitHub Issues (https://github.com/apache/activemq/issues)
> Jira is now read-only and we should now all use GitHub Issues.
>
> We have the following labels available:
> - bug: for bug reports
> - dependencies: for dependencies updates
> - enhancement: for improvements on existing code
> - feature: for a complete new features
> - proposal: for a design proposal, big features
> - stale: when the issue is "inactive" for more than 60 days
>
> Please use these labels to classify the issues.
>
> When you create a PR, you can associate it with an issue either in the
> GitHub UI or using "This closes #xxxx" in the comments.
> I also suggest using conventional commit messages in PR with the format
> <type>(<scope>): <subject> where scope is optional. The type can be:
> - feat: (a new feature is introduced with the changes)
> - fix: (bug fix has occurred, not a fix to a build script)
> - docs: (changes to the documentation)
> - style: (formatting, missing semicolons, etc; no production code change)
> - refactor: (refactoring production code, eg. renaming a variable)
> - test: (adding missing tests, refactoring tests; no production code
> change)
> - chore: (changes that do not relate to a fix or feature and don't modify
> src or test files (for example updating dependencies or change in
> production code))
> - perf – (performance improvements)
> - ci – (continuous integration related)
> - build – (changes that affect the build system or external dependencies)
> - revert – (reverts a previous commit)
> That's a nice practice because GitHub can use that to create nice Release
> Notes.
> Thanks to that, it's not necessary to create GH issues for all changes.
>
> For versions, we are using GitHub Projects (
> https://github.com/apache/activemq/projects?query=is%3Aopen).
> You can assign several projects/versions per issue, and track the status
> of the versions.
>
> 2. GitHub Discussions
> We also enabled GitHub Discussions where we can have technical discussions.
> The GH Discussions are automatically going to the dev@ mailing list.
>
> Let us know if you have any questions.
>
> Regards
> JB
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
If it’s up to me, I’m definitely in favor of switching to GitHub Issues.
KP
On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
dev@activemq.apache.org> wrote:
> Nice!
>
> Will all old Jira issues be migrated to GitHub too?
>
> Also, I'm wondering, how "stale" issues will be managed? I would hate to
> see those bots automatically closing issues if they are "inactive". I
> understand that sometimes there is a need to manage a backlog, but this
> doesn't allow "voting" on issues with likes or other means of activity
> other than "me too, please reopen" comments.
>
> --
> Best Regards,
> Vilius
>
> -----Original Message-----
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Thursday, February 19, 2026 6:42 PM
> To: dev@activemq.apache.org; users@activemq.apache.org
> Subject: GitHub Issues & Discussions enabled
>
> Hi folks,
>
> We are pleased to announce that GitHub Issues & Discussions.
>
> 1. GitHub Issues (https://github.com/apache/activemq/issues)
> Jira is now read-only and we should now all use GitHub Issues.
>
> We have the following labels available:
> - bug: for bug reports
> - dependencies: for dependencies updates
> - enhancement: for improvements on existing code
> - feature: for a complete new features
> - proposal: for a design proposal, big features
> - stale: when the issue is "inactive" for more than 60 days
>
> Please use these labels to classify the issues.
>
> When you create a PR, you can associate it with an issue either in the
> GitHub UI or using "This closes #xxxx" in the comments.
> I also suggest using conventional commit messages in PR with the format
> <type>(<scope>): <subject> where scope is optional. The type can be:
> - feat: (a new feature is introduced with the changes)
> - fix: (bug fix has occurred, not a fix to a build script)
> - docs: (changes to the documentation)
> - style: (formatting, missing semicolons, etc; no production code change)
> - refactor: (refactoring production code, eg. renaming a variable)
> - test: (adding missing tests, refactoring tests; no production code
> change)
> - chore: (changes that do not relate to a fix or feature and don't modify
> src or test files (for example updating dependencies or change in
> production code))
> - perf – (performance improvements)
> - ci – (continuous integration related)
> - build – (changes that affect the build system or external dependencies)
> - revert – (reverts a previous commit)
> That's a nice practice because GitHub can use that to create nice Release
> Notes.
> Thanks to that, it's not necessary to create GH issues for all changes.
>
> For versions, we are using GitHub Projects (
> https://github.com/apache/activemq/projects?query=is%3Aopen).
> You can assign several projects/versions per issue, and track the status
> of the versions.
>
> 2. GitHub Discussions
> We also enabled GitHub Discussions where we can have technical discussions.
> The GH Discussions are automatically going to the dev@ mailing list.
>
> Let us know if you have any questions.
>
> Regards
> JB
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
We have to create a ticket (Jira) to Infra team to do that.
Regards
JB
On Sun, May 31, 2026 at 11:13 PM Havret <ha...@apache.org> wrote:
>
> Hi JB,
> I've enabled issues and discussions on the other repositories. Can we mark jira for dotnet activemq components readonly the same way you marked activemq?
>
> Thanks,
> KP
>
> On Mon, May 11, 2026 at 5:25 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>
>> Hi
>>
>> GitHub Issues (and discussions) are now available for activemq-nms-api
>> repo: https://github.com/apache/activemq-nms-api/issues
>>
>> I will create the PRs on https://github.com/apache/activemq-nms-amqp and
>> https://github.com/apache/activemq-nms-openwire repositories.
>>
>> Regards
>> JB
>>
>> On Mon, May 11, 2026 at 5:20 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>> > Hi
>> >
>> > I went ahead and fixed the typo (missing space after :) on discussions.
>> >
>> > Regards
>> > JB
>> >
>> > On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
>> >
>> >> JB, I think we need some adjustments:
>> >>
>> >> while scanning a simple key
>> >> in "<byte string>", line 37, column 5:
>> >> discussions:true
>> >> ^
>> >> could not find expected ':'
>> >> in "<byte string>", line 39, column 1:
>> >> notifications:
>> >> ^
>> >>
>> >>
>> >> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> >> wrote:
>> >>
>> >> > Hi
>> >> >
>> >> > I created a first PR for nms-api repo:
>> >> > https://github.com/apache/activemq-nms-api/pull/35
>> >> >
>> >> > If it works for you, I will create the PRs for the other repos.
>> >> >
>> >> > Regards
>> >> > JB
>> >> >
>> >> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
>> >> >
>> >> > > Hi JB,
>> >> > >
>> >> > > Any update on this? Or any action needed from my end?
>> >> > >
>> >> > > Best,
>> >> > > KP
>> >> > >
>> >> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb@nanthrax.net
>> >> >
>> >> > > wrote:
>> >> > >
>> >> > > > Hi
>> >> > > >
>> >> > > > Sure, let me create the PRs for your review.
>> >> > > >
>> >> > > > Regards
>> >> > > > JB
>> >> > > >
>> >> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
>> >> > > >
>> >> > > > > Hi JB,
>> >> > > > >
>> >> > > > > Could you walk me through the process of enabling github issues
>> >> for:
>> >> > > > >
>> >> > > > > - https://github.com/apache/activemq-nms-api
>> >> > > > > - https://github.com/apache/activemq-nms-amqp
>> >> > > > > - https://github.com/apache/activemq-nms-openwire
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > KP
>> >> > > > >
>> >> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
>> >> > jb@nanthrax.net>
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > > > Hi
>> >> > > > > >
>> >> > > > > > 1. About stale: the stale issues are flagged by not closed (only
>> >> > the
>> >> > > PR
>> >> > > > > > could be closed by the stale bot). So the issues are still open
>> >> > (just
>> >> > > > > > flagged).
>> >> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
>> >> Jira
>> >> > > > > tickets
>> >> > > > > > to GH Issues. I'm creating issues manually for now (new
>> >> issues). I
>> >> > > will
>> >> > > > > run
>> >> > > > > > the migration soon. Again, Jira is still there, just read-only.
>> >> > > > > >
>> >> > > > > > Regards
>> >> > > > > > JB
>> >> > > > > >
>> >> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
>> >> > > > > > dev@activemq.apache.org> wrote:
>> >> > > > > >
>> >> > > > > > > Nice!
>> >> > > > > > >
>> >> > > > > > > Will all old Jira issues be migrated to GitHub too?
>> >> > > > > > >
>> >> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
>> >> would
>> >> > > hate
>> >> > > > > to
>> >> > > > > > > see those bots automatically closing issues if they are
>> >> > > "inactive". I
>> >> > > > > > > understand that sometimes there is a need to manage a backlog,
>> >> > but
>> >> > > > this
>> >> > > > > > > doesn't allow "voting" on issues with likes or other means of
>> >> > > > activity
>> >> > > > > > > other than "me too, please reopen" comments.
>> >> > > > > > >
>> >> > > > > > > --
>> >> > > > > > > Best Regards,
>> >> > > > > > > Vilius
>> >> > > > > > >
>> >> > > > > > > -----Original Message-----
>> >> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> >> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
>> >> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
>> >> > > > > > > Subject: GitHub Issues & Discussions enabled
>> >> > > > > > >
>> >> > > > > > > Hi folks,
>> >> > > > > > >
>> >> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
>> >> > > > > > >
>> >> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
>> >> > > > > > > Jira is now read-only and we should now all use GitHub Issues.
>> >> > > > > > >
>> >> > > > > > > We have the following labels available:
>> >> > > > > > > - bug: for bug reports
>> >> > > > > > > - dependencies: for dependencies updates
>> >> > > > > > > - enhancement: for improvements on existing code
>> >> > > > > > > - feature: for a complete new features
>> >> > > > > > > - proposal: for a design proposal, big features
>> >> > > > > > > - stale: when the issue is "inactive" for more than 60 days
>> >> > > > > > >
>> >> > > > > > > Please use these labels to classify the issues.
>> >> > > > > > >
>> >> > > > > > > When you create a PR, you can associate it with an issue
>> >> either
>> >> > in
>> >> > > > the
>> >> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
>> >> > > > > > > I also suggest using conventional commit messages in PR with
>> >> the
>> >> > > > format
>> >> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
>> >> can
>> >> > > be:
>> >> > > > > > > - feat: (a new feature is introduced with the changes)
>> >> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
>> >> > > > > > > - docs: (changes to the documentation)
>> >> > > > > > > - style: (formatting, missing semicolons, etc; no production
>> >> code
>> >> > > > > change)
>> >> > > > > > > - refactor: (refactoring production code, eg. renaming a
>> >> > variable)
>> >> > > > > > > - test: (adding missing tests, refactoring tests; no
>> >> production
>> >> > > code
>> >> > > > > > > change)
>> >> > > > > > > - chore: (changes that do not relate to a fix or feature and
>> >> > don't
>> >> > > > > modify
>> >> > > > > > > src or test files (for example updating dependencies or
>> >> change in
>> >> > > > > > > production code))
>> >> > > > > > > - perf – (performance improvements)
>> >> > > > > > > - ci – (continuous integration related)
>> >> > > > > > > - build – (changes that affect the build system or external
>> >> > > > > dependencies)
>> >> > > > > > > - revert – (reverts a previous commit)
>> >> > > > > > > That's a nice practice because GitHub can use that to create
>> >> nice
>> >> > > > > Release
>> >> > > > > > > Notes.
>> >> > > > > > > Thanks to that, it's not necessary to create GH issues for all
>> >> > > > changes.
>> >> > > > > > >
>> >> > > > > > > For versions, we are using GitHub Projects (
>> >> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
>> >> > > > > > > You can assign several projects/versions per issue, and track
>> >> the
>> >> > > > > status
>> >> > > > > > > of the versions.
>> >> > > > > > >
>> >> > > > > > > 2. GitHub Discussions
>> >> > > > > > > We also enabled GitHub Discussions where we can have technical
>> >> > > > > > discussions.
>> >> > > > > > > The GH Discussions are automatically going to the dev@
>> >> mailing
>> >> > > list.
>> >> > > > > > >
>> >> > > > > > > Let us know if you have any questions.
>> >> > > > > > >
>> >> > > > > > > Regards
>> >> > > > > > > JB
>> >> > > > > > >
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
Posted by Jason Jackson <ja...@itechag.com>.
I worked though my issues of permissions and authorizations.
The issue ended up being the way in which my users.properties and groups.properties where used.
The users.properties file was correct, the user must defined with the entire certificate own/detailed information.
I ended up setting my groups.properties the following way:
group=user
Once this was set I gave the group the permissions required within the activemq.xml file.
Jason
________________________________
From: Jason Jackson <ja...@itechag.com>
Sent: Thursday, June 11, 2026 2:56 PM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
I was able to finally get certificate authentication to work. An issue I was running in to was using Username/Password along with Certificate authentication.
What I had always used within my activemq.xml file had to change.
<jaasAuthenticationPlugin configuration"queueAuth"/>
This was my original setting and work for all transport connectors; I only use SSL transports. This allows for a username/password combination when connecting to the broker and accessing queues.
<jaasCertificateAuthenticationPlugin sslConfiguration="queueAuth"/>
This is the change I made to allow for certificates to perform mTLS but this also prevented username/password from working.
<jaasDualAuthenticationPlugin sslConfiguration="queueAuth"/>
The above setting is supposed to allow for either username/password or certificate authentication; this is what I am testing now and running into some issues.
Here is the setting I used on a test/development broker and it worked correctly.
users.properties
user=CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY
groups.properties
group=CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY
admins=admin,user,group
I was able to connect to the broker and queues to perform the actions I needed.
I have since removed the user and group from the admins entry and I am only assigning the permissions the user actually needed and running into a permissions error. I can see the user connect, I can see the certificate authentication succeeds, at this point the end use is prompted with a permissions error stating they do not have the rights needed/required.
Here are the permissions that I have set for the end user, any suggestions on what permissions I am missing?
<authorizationEntry queue="QUEUE_GET" read="user,group,admins" write="admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.Consumer.Queue.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.SlowConsumer.Queue.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempQueue.Queue.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempTopic.Topic.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry queue="QUEUE_PUT" read="admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.Producer.Queue.QUEUE_PUT" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempQueue.Queue.QUEUE_PUT" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempTopic.Topic.QUEUE_PUT" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempQueue" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempTopic" read="user,group,admins" write="user,group,admins" admin="admins"/>
Here is an example of the error that the end user receives.
Fatal JMS authorization error: user is not permitted to access the queue. Stopping program.
javax.jms.JMSSecurityException: User CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY is not authorized to read from: queue://QUEUE_GET
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:65) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1465) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1498) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:2159) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQMessageConsumer.<init>(ActiveMQMessageConsumer.java:294) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1326) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1269) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1181) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1153) ~[activemq-client-5.19.7.jar:5.19.7]
at application.activemq.Get.createConsumer(Get.java:898) ~[jmscommlib-1.0.0-SNAPSHOT.jar:?]
at application.activemq.Get.startReceive(Get.java:850) [jmscommlib-1.0.0-SNAPSHOT.jar:?]
at application.activemq.Get.setup(Get.java:381) [jmscommlib-1.0.0-SNAPSHOT.jar:?]
at application.activemq.Get.main(Get.java:289) [jmscommlib-1.0.0-SNAPSHOT.jar:?]
Caused by: java.lang.SecurityException: User CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY is not authorized
Any suggestions are appreciated.
Thank you.
Jason
________________________________
From: Christopher Shannon <ch...@gmail.com>
Sent: Thursday, June 11, 2026 11:08 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
EXTERNAL EMAIL - This email was sent by a person from outside your organization. Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity.
Secured by Check Point
So your certs are properly working now? It looked like the original
transport config was wrong, it should be
"transport.needClientAuth=true" on the URL but I'm guessing you
figured that out if it is working.
For the clients that it's failing username/password for when using
dual mode, is a cert still set by the client? Looking at the code it
will only process username and password if the client does not present
a certificate.
Chris
On Tue, Jun 9, 2026 at 2:11 PM Jason Jackson <ja...@itechag.com> wrote:
>
> Another update
>
> I now have the following configured and working
>
> activemq.xml
> <jaasDualAuthenticationPlugin configuration="queueUserModules" sslConfiguration="queueCertModules"/>
>
> The certificate base authentication works but the username and password authentication fails.
>
> Any configuration setting suggestions for the jaasDualAuthentication plugin
>
>
> Jason
>
>
> ________________________________
> From: Jason Jackson <ja...@itechag.com>
> Sent: Tuesday, June 9, 2026 1:16 PM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
>
> After continued troubleshooting and testing, I have been able to get mTLS to work.
>
> Here is how I was able to get mTLS to work correctly
>
> activemq.xml
> <jaasAuthenticationPlugin configuration="queueModules"/> --> <jaasCertificateAuthenticationPlugin configuration="queueModules"/>
>
> The issue I have now is I have some accounts that provide a username and password and also need the ability for Certificate base authentication.
>
> I have tried the following
>
> <jaasDualAuthenticationPlugin configuration="queueModules"/>
>
> This causes all authentication methods to fail; meaning username and password as well as certificate authentication all fail.
>
> Are there any suggestions on how to enable username and password along with certification authentication at the same time?
>
>
> Jason
>
>
> ________________________________
> From: Jason Jackson <ja...@itechag.com>
> Sent: Tuesday, June 9, 2026 9:40 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
>
> I am using ActiveMQ in a Linux environment with OpenJDK 17.x.
>
> I have a JAVA Client that is connecting to the ActiveMQ broker but fails to authenticate/authorize using mTLS using SSL Certificates. The client is able to reach the broker, perform all of the necessary handshakes, attempts the connection and fails on the authentication portion. I see all of the communication and failures within the broker log files and see the connection attempt.
>
> I have enabled debug logging on the client and broker, the client provides the following information:
>
> Caused by: java.lang.SecurityException: User name [null] or password is invalid.
>
> Looking through the broker log files I see the client connection and see that userName = null and password = ****. From the documentation I found this is expected if JAAS is configured for certificate authentication.
>
> The client logs the additional information after the above:
>
> Caused by: javax.security.auth.login.LoginException: Client certificates not found. Cannot authenticate
>
> My client and broker certificates have the following:
>
>
> 1.
> Client/server certificates
> 2.
> X.509 certificates
> 3.
> Signed by the same intermediate
> 4.
> Signed by the same root
>
> I am using the same P12 for the keystore and truststore, I am not sure if these must be separated for mTLS to function correctly.
>
> My broker transport is configured the following way
>
> activemq.xml
> <transportConnectors>
> <transportConnector name="nio+ssl_6161" uri="nio+ssl://host_name:6161?verifyHostName=false&needClientAuth=true"/>
> </transportConnectors>
>
> login.conf
> certModule (Tried this the first time)
> {
> org.apache.activemq.jaas.TextFileCertificateLoginModule required
> org.apache.activemq.jaas.textfiledn.user=users.properties
> org.apache.activemq.jaas.textfiledn.group=groups.properties
> }
>
> certModule (Tried this the second time)
> {
> org.apache.activemq.jaas.CertificateLoginModule required
> org.apache.activemq.jaas.textfiledn.user=users.properties
> org.apache.activemq.jaas.textfiledn.group=groups.properties
> }
>
> users.properties
> partner=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
>
> groups.propertiesd
> partnerg=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
> Admin=admin,partner,partnerg
>
>
> The JAVA ActiveMQ client has the following set and connects using the following options:
>
> String brokerConnection = "nio+ssl://host_name:6161"?verifyHostName=false;
> ActiveMQSslConnectionFactory connectionFactory = new ActiveMQSslConnectionFactory(brokerConnection);
> connectionFactory.setKeyStore("myKeyStore.p12");
> connectionFactory.setKeyStorePassword("myPassword");
> connectionFactory.setKeyStoreType("PKCS12");
> connectionFactory.setTrustStore("myKeyStore.p12");
> connectionFactory.setTrustStorePassword("myPassword");
> connectionFactory.setTrustStoreType("PKCS12");
> Connection connection = connectionFactory.createConnection();
> connection.start();
> session = connection.CreateSession(false, Session.Auto_ACKNOWLEDGE);
>
> What am I missing on the client or broker side that would allow mTLS to be successful?
>
>
>
> Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
Posted by Jason Jackson <ja...@itechag.com>.
I was able to finally get certificate authentication to work. An issue I was running in to was using Username/Password along with Certificate authentication.
What I had always used within my activemq.xml file had to change.
<jaasAuthenticationPlugin configuration"queueAuth"/>
This was my original setting and work for all transport connectors; I only use SSL transports. This allows for a username/password combination when connecting to the broker and accessing queues.
<jaasCertificateAuthenticationPlugin sslConfiguration="queueAuth"/>
This is the change I made to allow for certificates to perform mTLS but this also prevented username/password from working.
<jaasDualAuthenticationPlugin sslConfiguration="queueAuth"/>
The above setting is supposed to allow for either username/password or certificate authentication; this is what I am testing now and running into some issues.
Here is the setting I used on a test/development broker and it worked correctly.
users.properties
user=CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY
groups.properties
group=CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY
admins=admin,user,group
I was able to connect to the broker and queues to perform the actions I needed.
I have since removed the user and group from the admins entry and I am only assigning the permissions the user actually needed and running into a permissions error. I can see the user connect, I can see the certificate authentication succeeds, at this point the end use is prompted with a permissions error stating they do not have the rights needed/required.
Here are the permissions that I have set for the end user, any suggestions on what permissions I am missing?
<authorizationEntry queue="QUEUE_GET" read="user,group,admins" write="admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.Consumer.Queue.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.SlowConsumer.Queue.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempQueue.Queue.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempTopic.Topic.QUEUE_GET" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry queue="QUEUE_PUT" read="admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.Producer.Queue.QUEUE_PUT" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempQueue.Queue.QUEUE_PUT" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempTopic.Topic.QUEUE_PUT" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempQueue" read="user,group,admins" write="user,group,admins" admin="admins"/>
<authorizationEntry topic="ActiveMQ.Advisory.TempTopic" read="user,group,admins" write="user,group,admins" admin="admins"/>
Here is an example of the error that the end user receives.
Fatal JMS authorization error: user is not permitted to access the queue. Stopping program.
javax.jms.JMSSecurityException: User CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY is not authorized to read from: queue://QUEUE_GET
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:65) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1465) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1498) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.syncSendPacket(ActiveMQSession.java:2159) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQMessageConsumer.<init>(ActiveMQMessageConsumer.java:294) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1326) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1269) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1181) ~[activemq-client-5.19.7.jar:5.19.7]
at org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1153) ~[activemq-client-5.19.7.jar:5.19.7]
at application.activemq.Get.createConsumer(Get.java:898) ~[jmscommlib-1.0.0-SNAPSHOT.jar:?]
at application.activemq.Get.startReceive(Get.java:850) [jmscommlib-1.0.0-SNAPSHOT.jar:?]
at application.activemq.Get.setup(Get.java:381) [jmscommlib-1.0.0-SNAPSHOT.jar:?]
at application.activemq.Get.main(Get.java:289) [jmscommlib-1.0.0-SNAPSHOT.jar:?]
Caused by: java.lang.SecurityException: User CN=MY_CERT, OU=MY_OU, O=MY_O, L=MY_LOCATION, ST=MY_STATE, C=MY_COUNTRY is not authorized
Any suggestions are appreciated.
Thank you.
Jason
________________________________
From: Christopher Shannon <ch...@gmail.com>
Sent: Thursday, June 11, 2026 11:08 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
EXTERNAL EMAIL - This email was sent by a person from outside your organization. Exercise caution when clicking links, opening attachments or taking further action, before validating its authenticity.
Secured by Check Point
So your certs are properly working now? It looked like the original
transport config was wrong, it should be
"transport.needClientAuth=true" on the URL but I'm guessing you
figured that out if it is working.
For the clients that it's failing username/password for when using
dual mode, is a cert still set by the client? Looking at the code it
will only process username and password if the client does not present
a certificate.
Chris
On Tue, Jun 9, 2026 at 2:11 PM Jason Jackson <ja...@itechag.com> wrote:
>
> Another update
>
> I now have the following configured and working
>
> activemq.xml
> <jaasDualAuthenticationPlugin configuration="queueUserModules" sslConfiguration="queueCertModules"/>
>
> The certificate base authentication works but the username and password authentication fails.
>
> Any configuration setting suggestions for the jaasDualAuthentication plugin
>
>
> Jason
>
>
> ________________________________
> From: Jason Jackson <ja...@itechag.com>
> Sent: Tuesday, June 9, 2026 1:16 PM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
>
> After continued troubleshooting and testing, I have been able to get mTLS to work.
>
> Here is how I was able to get mTLS to work correctly
>
> activemq.xml
> <jaasAuthenticationPlugin configuration="queueModules"/> --> <jaasCertificateAuthenticationPlugin configuration="queueModules"/>
>
> The issue I have now is I have some accounts that provide a username and password and also need the ability for Certificate base authentication.
>
> I have tried the following
>
> <jaasDualAuthenticationPlugin configuration="queueModules"/>
>
> This causes all authentication methods to fail; meaning username and password as well as certificate authentication all fail.
>
> Are there any suggestions on how to enable username and password along with certification authentication at the same time?
>
>
> Jason
>
>
> ________________________________
> From: Jason Jackson <ja...@itechag.com>
> Sent: Tuesday, June 9, 2026 9:40 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
>
> I am using ActiveMQ in a Linux environment with OpenJDK 17.x.
>
> I have a JAVA Client that is connecting to the ActiveMQ broker but fails to authenticate/authorize using mTLS using SSL Certificates. The client is able to reach the broker, perform all of the necessary handshakes, attempts the connection and fails on the authentication portion. I see all of the communication and failures within the broker log files and see the connection attempt.
>
> I have enabled debug logging on the client and broker, the client provides the following information:
>
> Caused by: java.lang.SecurityException: User name [null] or password is invalid.
>
> Looking through the broker log files I see the client connection and see that userName = null and password = ****. From the documentation I found this is expected if JAAS is configured for certificate authentication.
>
> The client logs the additional information after the above:
>
> Caused by: javax.security.auth.login.LoginException: Client certificates not found. Cannot authenticate
>
> My client and broker certificates have the following:
>
>
> 1.
> Client/server certificates
> 2.
> X.509 certificates
> 3.
> Signed by the same intermediate
> 4.
> Signed by the same root
>
> I am using the same P12 for the keystore and truststore, I am not sure if these must be separated for mTLS to function correctly.
>
> My broker transport is configured the following way
>
> activemq.xml
> <transportConnectors>
> <transportConnector name="nio+ssl_6161" uri="nio+ssl://host_name:6161?verifyHostName=false&needClientAuth=true"/>
> </transportConnectors>
>
> login.conf
> certModule (Tried this the first time)
> {
> org.apache.activemq.jaas.TextFileCertificateLoginModule required
> org.apache.activemq.jaas.textfiledn.user=users.properties
> org.apache.activemq.jaas.textfiledn.group=groups.properties
> }
>
> certModule (Tried this the second time)
> {
> org.apache.activemq.jaas.CertificateLoginModule required
> org.apache.activemq.jaas.textfiledn.user=users.properties
> org.apache.activemq.jaas.textfiledn.group=groups.properties
> }
>
> users.properties
> partner=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
>
> groups.propertiesd
> partnerg=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
> Admin=admin,partner,partnerg
>
>
> The JAVA ActiveMQ client has the following set and connects using the following options:
>
> String brokerConnection = "nio+ssl://host_name:6161"?verifyHostName=false;
> ActiveMQSslConnectionFactory connectionFactory = new ActiveMQSslConnectionFactory(brokerConnection);
> connectionFactory.setKeyStore("myKeyStore.p12");
> connectionFactory.setKeyStorePassword("myPassword");
> connectionFactory.setKeyStoreType("PKCS12");
> connectionFactory.setTrustStore("myKeyStore.p12");
> connectionFactory.setTrustStorePassword("myPassword");
> connectionFactory.setTrustStoreType("PKCS12");
> Connection connection = connectionFactory.createConnection();
> connection.start();
> session = connection.CreateSession(false, Session.Auto_ACKNOWLEDGE);
>
> What am I missing on the client or broker side that would allow mTLS to be successful?
>
>
>
> Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
Posted by Christopher Shannon <ch...@gmail.com>.
So your certs are properly working now? It looked like the original
transport config was wrong, it should be
"transport.needClientAuth=true" on the URL but I'm guessing you
figured that out if it is working.
For the clients that it's failing username/password for when using
dual mode, is a cert still set by the client? Looking at the code it
will only process username and password if the client does not present
a certificate.
Chris
On Tue, Jun 9, 2026 at 2:11 PM Jason Jackson <ja...@itechag.com> wrote:
>
> Another update
>
> I now have the following configured and working
>
> activemq.xml
> <jaasDualAuthenticationPlugin configuration="queueUserModules" sslConfiguration="queueCertModules"/>
>
> The certificate base authentication works but the username and password authentication fails.
>
> Any configuration setting suggestions for the jaasDualAuthentication plugin
>
>
> Jason
>
>
> ________________________________
> From: Jason Jackson <ja...@itechag.com>
> Sent: Tuesday, June 9, 2026 1:16 PM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
>
> After continued troubleshooting and testing, I have been able to get mTLS to work.
>
> Here is how I was able to get mTLS to work correctly
>
> activemq.xml
> <jaasAuthenticationPlugin configuration="queueModules"/> --> <jaasCertificateAuthenticationPlugin configuration="queueModules"/>
>
> The issue I have now is I have some accounts that provide a username and password and also need the ability for Certificate base authentication.
>
> I have tried the following
>
> <jaasDualAuthenticationPlugin configuration="queueModules"/>
>
> This causes all authentication methods to fail; meaning username and password as well as certificate authentication all fail.
>
> Are there any suggestions on how to enable username and password along with certification authentication at the same time?
>
>
> Jason
>
>
> ________________________________
> From: Jason Jackson <ja...@itechag.com>
> Sent: Tuesday, June 9, 2026 9:40 AM
> To: users@activemq.apache.org <us...@activemq.apache.org>
> Subject: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
>
> I am using ActiveMQ in a Linux environment with OpenJDK 17.x.
>
> I have a JAVA Client that is connecting to the ActiveMQ broker but fails to authenticate/authorize using mTLS using SSL Certificates. The client is able to reach the broker, perform all of the necessary handshakes, attempts the connection and fails on the authentication portion. I see all of the communication and failures within the broker log files and see the connection attempt.
>
> I have enabled debug logging on the client and broker, the client provides the following information:
>
> Caused by: java.lang.SecurityException: User name [null] or password is invalid.
>
> Looking through the broker log files I see the client connection and see that userName = null and password = ****. From the documentation I found this is expected if JAAS is configured for certificate authentication.
>
> The client logs the additional information after the above:
>
> Caused by: javax.security.auth.login.LoginException: Client certificates not found. Cannot authenticate
>
> My client and broker certificates have the following:
>
>
> 1.
> Client/server certificates
> 2.
> X.509 certificates
> 3.
> Signed by the same intermediate
> 4.
> Signed by the same root
>
> I am using the same P12 for the keystore and truststore, I am not sure if these must be separated for mTLS to function correctly.
>
> My broker transport is configured the following way
>
> activemq.xml
> <transportConnectors>
> <transportConnector name="nio+ssl_6161" uri="nio+ssl://host_name:6161?verifyHostName=false&needClientAuth=true"/>
> </transportConnectors>
>
> login.conf
> certModule (Tried this the first time)
> {
> org.apache.activemq.jaas.TextFileCertificateLoginModule required
> org.apache.activemq.jaas.textfiledn.user=users.properties
> org.apache.activemq.jaas.textfiledn.group=groups.properties
> }
>
> certModule (Tried this the second time)
> {
> org.apache.activemq.jaas.CertificateLoginModule required
> org.apache.activemq.jaas.textfiledn.user=users.properties
> org.apache.activemq.jaas.textfiledn.group=groups.properties
> }
>
> users.properties
> partner=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
>
> groups.propertiesd
> partnerg=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
> Admin=admin,partner,partnerg
>
>
> The JAVA ActiveMQ client has the following set and connects using the following options:
>
> String brokerConnection = "nio+ssl://host_name:6161"?verifyHostName=false;
> ActiveMQSslConnectionFactory connectionFactory = new ActiveMQSslConnectionFactory(brokerConnection);
> connectionFactory.setKeyStore("myKeyStore.p12");
> connectionFactory.setKeyStorePassword("myPassword");
> connectionFactory.setKeyStoreType("PKCS12");
> connectionFactory.setTrustStore("myKeyStore.p12");
> connectionFactory.setTrustStorePassword("myPassword");
> connectionFactory.setTrustStoreType("PKCS12");
> Connection connection = connectionFactory.createConnection();
> connection.start();
> session = connection.CreateSession(false, Session.Auto_ACKNOWLEDGE);
>
> What am I missing on the client or broker side that would allow mTLS to be successful?
>
>
>
> Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
Posted by Jason Jackson <ja...@itechag.com>.
Another update
I now have the following configured and working
activemq.xml
<jaasDualAuthenticationPlugin configuration="queueUserModules" sslConfiguration="queueCertModules"/>
The certificate base authentication works but the username and password authentication fails.
Any configuration setting suggestions for the jaasDualAuthentication plugin
Jason
________________________________
From: Jason Jackson <ja...@itechag.com>
Sent: Tuesday, June 9, 2026 1:16 PM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
After continued troubleshooting and testing, I have been able to get mTLS to work.
Here is how I was able to get mTLS to work correctly
activemq.xml
<jaasAuthenticationPlugin configuration="queueModules"/> --> <jaasCertificateAuthenticationPlugin configuration="queueModules"/>
The issue I have now is I have some accounts that provide a username and password and also need the ability for Certificate base authentication.
I have tried the following
<jaasDualAuthenticationPlugin configuration="queueModules"/>
This causes all authentication methods to fail; meaning username and password as well as certificate authentication all fail.
Are there any suggestions on how to enable username and password along with certification authentication at the same time?
Jason
________________________________
From: Jason Jackson <ja...@itechag.com>
Sent: Tuesday, June 9, 2026 9:40 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
I am using ActiveMQ in a Linux environment with OpenJDK 17.x.
I have a JAVA Client that is connecting to the ActiveMQ broker but fails to authenticate/authorize using mTLS using SSL Certificates. The client is able to reach the broker, perform all of the necessary handshakes, attempts the connection and fails on the authentication portion. I see all of the communication and failures within the broker log files and see the connection attempt.
I have enabled debug logging on the client and broker, the client provides the following information:
Caused by: java.lang.SecurityException: User name [null] or password is invalid.
Looking through the broker log files I see the client connection and see that userName = null and password = ****. From the documentation I found this is expected if JAAS is configured for certificate authentication.
The client logs the additional information after the above:
Caused by: javax.security.auth.login.LoginException: Client certificates not found. Cannot authenticate
My client and broker certificates have the following:
1.
Client/server certificates
2.
X.509 certificates
3.
Signed by the same intermediate
4.
Signed by the same root
I am using the same P12 for the keystore and truststore, I am not sure if these must be separated for mTLS to function correctly.
My broker transport is configured the following way
activemq.xml
<transportConnectors>
<transportConnector name="nio+ssl_6161" uri="nio+ssl://host_name:6161?verifyHostName=false&needClientAuth=true"/>
</transportConnectors>
login.conf
certModule (Tried this the first time)
{
org.apache.activemq.jaas.TextFileCertificateLoginModule required
org.apache.activemq.jaas.textfiledn.user=users.properties
org.apache.activemq.jaas.textfiledn.group=groups.properties
}
certModule (Tried this the second time)
{
org.apache.activemq.jaas.CertificateLoginModule required
org.apache.activemq.jaas.textfiledn.user=users.properties
org.apache.activemq.jaas.textfiledn.group=groups.properties
}
users.properties
partner=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
groups.propertiesd
partnerg=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
Admin=admin,partner,partnerg
The JAVA ActiveMQ client has the following set and connects using the following options:
String brokerConnection = "nio+ssl://host_name:6161"?verifyHostName=false;
ActiveMQSslConnectionFactory connectionFactory = new ActiveMQSslConnectionFactory(brokerConnection);
connectionFactory.setKeyStore("myKeyStore.p12");
connectionFactory.setKeyStorePassword("myPassword");
connectionFactory.setKeyStoreType("PKCS12");
connectionFactory.setTrustStore("myKeyStore.p12");
connectionFactory.setTrustStorePassword("myPassword");
connectionFactory.setTrustStoreType("PKCS12");
Connection connection = connectionFactory.createConnection();
connection.start();
session = connection.CreateSession(false, Session.Auto_ACKNOWLEDGE);
What am I missing on the client or broker side that would allow mTLS to be successful?
Jason
Re: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
Posted by Jason Jackson <ja...@itechag.com>.
After continued troubleshooting and testing, I have been able to get mTLS to work.
Here is how I was able to get mTLS to work correctly
activemq.xml
<jaasAuthenticationPlugin configuration="queueModules"/> --> <jaasCertificateAuthenticationPlugin configuration="queueModules"/>
The issue I have now is I have some accounts that provide a username and password and also need the ability for Certificate base authentication.
I have tried the following
<jaasDualAuthenticationPlugin configuration="queueModules"/>
This causes all authentication methods to fail; meaning username and password as well as certificate authentication all fail.
Are there any suggestions on how to enable username and password along with certification authentication at the same time?
Jason
________________________________
From: Jason Jackson <ja...@itechag.com>
Sent: Tuesday, June 9, 2026 9:40 AM
To: users@activemq.apache.org <us...@activemq.apache.org>
Subject: ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
I am using ActiveMQ in a Linux environment with OpenJDK 17.x.
I have a JAVA Client that is connecting to the ActiveMQ broker but fails to authenticate/authorize using mTLS using SSL Certificates. The client is able to reach the broker, perform all of the necessary handshakes, attempts the connection and fails on the authentication portion. I see all of the communication and failures within the broker log files and see the connection attempt.
I have enabled debug logging on the client and broker, the client provides the following information:
Caused by: java.lang.SecurityException: User name [null] or password is invalid.
Looking through the broker log files I see the client connection and see that userName = null and password = ****. From the documentation I found this is expected if JAAS is configured for certificate authentication.
The client logs the additional information after the above:
Caused by: javax.security.auth.login.LoginException: Client certificates not found. Cannot authenticate
My client and broker certificates have the following:
1.
Client/server certificates
2.
X.509 certificates
3.
Signed by the same intermediate
4.
Signed by the same root
I am using the same P12 for the keystore and truststore, I am not sure if these must be separated for mTLS to function correctly.
My broker transport is configured the following way
activemq.xml
<transportConnectors>
<transportConnector name="nio+ssl_6161" uri="nio+ssl://host_name:6161?verifyHostName=false&needClientAuth=true"/>
</transportConnectors>
login.conf
certModule (Tried this the first time)
{
org.apache.activemq.jaas.TextFileCertificateLoginModule required
org.apache.activemq.jaas.textfiledn.user=users.properties
org.apache.activemq.jaas.textfiledn.group=groups.properties
}
certModule (Tried this the second time)
{
org.apache.activemq.jaas.CertificateLoginModule required
org.apache.activemq.jaas.textfiledn.user=users.properties
org.apache.activemq.jaas.textfiledn.group=groups.properties
}
users.properties
partner=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
groups.propertiesd
partnerg=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
Admin=admin,partner,partnerg
The JAVA ActiveMQ client has the following set and connects using the following options:
String brokerConnection = "nio+ssl://host_name:6161"?verifyHostName=false;
ActiveMQSslConnectionFactory connectionFactory = new ActiveMQSslConnectionFactory(brokerConnection);
connectionFactory.setKeyStore("myKeyStore.p12");
connectionFactory.setKeyStorePassword("myPassword");
connectionFactory.setKeyStoreType("PKCS12");
connectionFactory.setTrustStore("myKeyStore.p12");
connectionFactory.setTrustStorePassword("myPassword");
connectionFactory.setTrustStoreType("PKCS12");
Connection connection = connectionFactory.createConnection();
connection.start();
session = connection.CreateSession(false, Session.Auto_ACKNOWLEDGE);
What am I missing on the client or broker side that would allow mTLS to be successful?
Jason
ActiveMQ Classic 6.2.6 mTLS Failure and Assistance
Posted by Jason Jackson <ja...@itechag.com>.
I am using ActiveMQ in a Linux environment with OpenJDK 17.x.
I have a JAVA Client that is connecting to the ActiveMQ broker but fails to authenticate/authorize using mTLS using SSL Certificates. The client is able to reach the broker, perform all of the necessary handshakes, attempts the connection and fails on the authentication portion. I see all of the communication and failures within the broker log files and see the connection attempt.
I have enabled debug logging on the client and broker, the client provides the following information:
Caused by: java.lang.SecurityException: User name [null] or password is invalid.
Looking through the broker log files I see the client connection and see that userName = null and password = ****. From the documentation I found this is expected if JAAS is configured for certificate authentication.
The client logs the additional information after the above:
Caused by: javax.security.auth.login.LoginException: Client certificates not found. Cannot authenticate
My client and broker certificates have the following:
1.
Client/server certificates
2.
X.509 certificates
3.
Signed by the same intermediate
4.
Signed by the same root
I am using the same P12 for the keystore and truststore, I am not sure if these must be separated for mTLS to function correctly.
My broker transport is configured the following way
activemq.xml
<transportConnectors>
<transportConnector name="nio+ssl_6161" uri="nio+ssl://host_name:6161?verifyHostName=false&needClientAuth=true"/>
</transportConnectors>
login.conf
certModule (Tried this the first time)
{
org.apache.activemq.jaas.TextFileCertificateLoginModule required
org.apache.activemq.jaas.textfiledn.user=users.properties
org.apache.activemq.jaas.textfiledn.group=groups.properties
}
certModule (Tried this the second time)
{
org.apache.activemq.jaas.CertificateLoginModule required
org.apache.activemq.jaas.textfiledn.user=users.properties
org.apache.activemq.jaas.textfiledn.group=groups.properties
}
users.properties
partner=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
groups.propertiesd
partnerg=CN=PARTNER, OU=My Sub Org, O=My Org, L=City, ST=State, C=Country
Admin=admin,partner,partnerg
The JAVA ActiveMQ client has the following set and connects using the following options:
String brokerConnection = "nio+ssl://host_name:6161"?verifyHostName=false;
ActiveMQSslConnectionFactory connectionFactory = new ActiveMQSslConnectionFactory(brokerConnection);
connectionFactory.setKeyStore("myKeyStore.p12");
connectionFactory.setKeyStorePassword("myPassword");
connectionFactory.setKeyStoreType("PKCS12");
connectionFactory.setTrustStore("myKeyStore.p12");
connectionFactory.setTrustStorePassword("myPassword");
connectionFactory.setTrustStoreType("PKCS12");
Connection connection = connectionFactory.createConnection();
connection.start();
session = connection.CreateSession(false, Session.Auto_ACKNOWLEDGE);
What am I missing on the client or broker side that would allow mTLS to be successful?
Jason
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
We have to create a ticket (Jira) to Infra team to do that.
Regards
JB
On Sun, May 31, 2026 at 11:13 PM Havret <ha...@apache.org> wrote:
>
> Hi JB,
> I've enabled issues and discussions on the other repositories. Can we mark jira for dotnet activemq components readonly the same way you marked activemq?
>
> Thanks,
> KP
>
> On Mon, May 11, 2026 at 5:25 AM Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>
>> Hi
>>
>> GitHub Issues (and discussions) are now available for activemq-nms-api
>> repo: https://github.com/apache/activemq-nms-api/issues
>>
>> I will create the PRs on https://github.com/apache/activemq-nms-amqp and
>> https://github.com/apache/activemq-nms-openwire repositories.
>>
>> Regards
>> JB
>>
>> On Mon, May 11, 2026 at 5:20 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>> > Hi
>> >
>> > I went ahead and fixed the typo (missing space after :) on discussions.
>> >
>> > Regards
>> > JB
>> >
>> > On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
>> >
>> >> JB, I think we need some adjustments:
>> >>
>> >> while scanning a simple key
>> >> in "<byte string>", line 37, column 5:
>> >> discussions:true
>> >> ^
>> >> could not find expected ':'
>> >> in "<byte string>", line 39, column 1:
>> >> notifications:
>> >> ^
>> >>
>> >>
>> >> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> >> wrote:
>> >>
>> >> > Hi
>> >> >
>> >> > I created a first PR for nms-api repo:
>> >> > https://github.com/apache/activemq-nms-api/pull/35
>> >> >
>> >> > If it works for you, I will create the PRs for the other repos.
>> >> >
>> >> > Regards
>> >> > JB
>> >> >
>> >> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
>> >> >
>> >> > > Hi JB,
>> >> > >
>> >> > > Any update on this? Or any action needed from my end?
>> >> > >
>> >> > > Best,
>> >> > > KP
>> >> > >
>> >> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb@nanthrax.net
>> >> >
>> >> > > wrote:
>> >> > >
>> >> > > > Hi
>> >> > > >
>> >> > > > Sure, let me create the PRs for your review.
>> >> > > >
>> >> > > > Regards
>> >> > > > JB
>> >> > > >
>> >> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
>> >> > > >
>> >> > > > > Hi JB,
>> >> > > > >
>> >> > > > > Could you walk me through the process of enabling github issues
>> >> for:
>> >> > > > >
>> >> > > > > - https://github.com/apache/activemq-nms-api
>> >> > > > > - https://github.com/apache/activemq-nms-amqp
>> >> > > > > - https://github.com/apache/activemq-nms-openwire
>> >> > > > >
>> >> > > > > Thanks,
>> >> > > > > KP
>> >> > > > >
>> >> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
>> >> > jb@nanthrax.net>
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > > > Hi
>> >> > > > > >
>> >> > > > > > 1. About stale: the stale issues are flagged by not closed (only
>> >> > the
>> >> > > PR
>> >> > > > > > could be closed by the stale bot). So the issues are still open
>> >> > (just
>> >> > > > > > flagged).
>> >> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
>> >> Jira
>> >> > > > > tickets
>> >> > > > > > to GH Issues. I'm creating issues manually for now (new
>> >> issues). I
>> >> > > will
>> >> > > > > run
>> >> > > > > > the migration soon. Again, Jira is still there, just read-only.
>> >> > > > > >
>> >> > > > > > Regards
>> >> > > > > > JB
>> >> > > > > >
>> >> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
>> >> > > > > > dev@activemq.apache.org> wrote:
>> >> > > > > >
>> >> > > > > > > Nice!
>> >> > > > > > >
>> >> > > > > > > Will all old Jira issues be migrated to GitHub too?
>> >> > > > > > >
>> >> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
>> >> would
>> >> > > hate
>> >> > > > > to
>> >> > > > > > > see those bots automatically closing issues if they are
>> >> > > "inactive". I
>> >> > > > > > > understand that sometimes there is a need to manage a backlog,
>> >> > but
>> >> > > > this
>> >> > > > > > > doesn't allow "voting" on issues with likes or other means of
>> >> > > > activity
>> >> > > > > > > other than "me too, please reopen" comments.
>> >> > > > > > >
>> >> > > > > > > --
>> >> > > > > > > Best Regards,
>> >> > > > > > > Vilius
>> >> > > > > > >
>> >> > > > > > > -----Original Message-----
>> >> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> >> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
>> >> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
>> >> > > > > > > Subject: GitHub Issues & Discussions enabled
>> >> > > > > > >
>> >> > > > > > > Hi folks,
>> >> > > > > > >
>> >> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
>> >> > > > > > >
>> >> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
>> >> > > > > > > Jira is now read-only and we should now all use GitHub Issues.
>> >> > > > > > >
>> >> > > > > > > We have the following labels available:
>> >> > > > > > > - bug: for bug reports
>> >> > > > > > > - dependencies: for dependencies updates
>> >> > > > > > > - enhancement: for improvements on existing code
>> >> > > > > > > - feature: for a complete new features
>> >> > > > > > > - proposal: for a design proposal, big features
>> >> > > > > > > - stale: when the issue is "inactive" for more than 60 days
>> >> > > > > > >
>> >> > > > > > > Please use these labels to classify the issues.
>> >> > > > > > >
>> >> > > > > > > When you create a PR, you can associate it with an issue
>> >> either
>> >> > in
>> >> > > > the
>> >> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
>> >> > > > > > > I also suggest using conventional commit messages in PR with
>> >> the
>> >> > > > format
>> >> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
>> >> can
>> >> > > be:
>> >> > > > > > > - feat: (a new feature is introduced with the changes)
>> >> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
>> >> > > > > > > - docs: (changes to the documentation)
>> >> > > > > > > - style: (formatting, missing semicolons, etc; no production
>> >> code
>> >> > > > > change)
>> >> > > > > > > - refactor: (refactoring production code, eg. renaming a
>> >> > variable)
>> >> > > > > > > - test: (adding missing tests, refactoring tests; no
>> >> production
>> >> > > code
>> >> > > > > > > change)
>> >> > > > > > > - chore: (changes that do not relate to a fix or feature and
>> >> > don't
>> >> > > > > modify
>> >> > > > > > > src or test files (for example updating dependencies or
>> >> change in
>> >> > > > > > > production code))
>> >> > > > > > > - perf – (performance improvements)
>> >> > > > > > > - ci – (continuous integration related)
>> >> > > > > > > - build – (changes that affect the build system or external
>> >> > > > > dependencies)
>> >> > > > > > > - revert – (reverts a previous commit)
>> >> > > > > > > That's a nice practice because GitHub can use that to create
>> >> nice
>> >> > > > > Release
>> >> > > > > > > Notes.
>> >> > > > > > > Thanks to that, it's not necessary to create GH issues for all
>> >> > > > changes.
>> >> > > > > > >
>> >> > > > > > > For versions, we are using GitHub Projects (
>> >> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
>> >> > > > > > > You can assign several projects/versions per issue, and track
>> >> the
>> >> > > > > status
>> >> > > > > > > of the versions.
>> >> > > > > > >
>> >> > > > > > > 2. GitHub Discussions
>> >> > > > > > > We also enabled GitHub Discussions where we can have technical
>> >> > > > > > discussions.
>> >> > > > > > > The GH Discussions are automatically going to the dev@
>> >> mailing
>> >> > > list.
>> >> > > > > > >
>> >> > > > > > > Let us know if you have any questions.
>> >> > > > > > >
>> >> > > > > > > Regards
>> >> > > > > > > JB
>> >> > > > > > >
>> >> > > > > >
>> >> > > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
I've enabled issues and discussions on the other repositories. Can we mark
jira for dotnet activemq components readonly the same way you marked
activemq?
Thanks,
KP
On Mon, May 11, 2026 at 5:25 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> GitHub Issues (and discussions) are now available for activemq-nms-api
> repo: https://github.com/apache/activemq-nms-api/issues
>
> I will create the PRs on https://github.com/apache/activemq-nms-amqp and
> https://github.com/apache/activemq-nms-openwire repositories.
>
> Regards
> JB
>
> On Mon, May 11, 2026 at 5:20 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > I went ahead and fixed the typo (missing space after :) on discussions.
> >
> > Regards
> > JB
> >
> > On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
> >
> >> JB, I think we need some adjustments:
> >>
> >> while scanning a simple key
> >> in "<byte string>", line 37, column 5:
> >> discussions:true
> >> ^
> >> could not find expected ':'
> >> in "<byte string>", line 39, column 1:
> >> notifications:
> >> ^
> >>
> >>
> >> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >>
> >> > Hi
> >> >
> >> > I created a first PR for nms-api repo:
> >> > https://github.com/apache/activemq-nms-api/pull/35
> >> >
> >> > If it works for you, I will create the PRs for the other repos.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
> >> >
> >> > > Hi JB,
> >> > >
> >> > > Any update on this? Or any action needed from my end?
> >> > >
> >> > > Best,
> >> > > KP
> >> > >
> >> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <
> jb@nanthrax.net
> >> >
> >> > > wrote:
> >> > >
> >> > > > Hi
> >> > > >
> >> > > > Sure, let me create the PRs for your review.
> >> > > >
> >> > > > Regards
> >> > > > JB
> >> > > >
> >> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org>
> wrote:
> >> > > >
> >> > > > > Hi JB,
> >> > > > >
> >> > > > > Could you walk me through the process of enabling github issues
> >> for:
> >> > > > >
> >> > > > > - https://github.com/apache/activemq-nms-api
> >> > > > > - https://github.com/apache/activemq-nms-amqp
> >> > > > > - https://github.com/apache/activemq-nms-openwire
> >> > > > >
> >> > > > > Thanks,
> >> > > > > KP
> >> > > > >
> >> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
> >> > jb@nanthrax.net>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Hi
> >> > > > > >
> >> > > > > > 1. About stale: the stale issues are flagged by not closed
> (only
> >> > the
> >> > > PR
> >> > > > > > could be closed by the stale bot). So the issues are still
> open
> >> > (just
> >> > > > > > flagged).
> >> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
> >> Jira
> >> > > > > tickets
> >> > > > > > to GH Issues. I'm creating issues manually for now (new
> >> issues). I
> >> > > will
> >> > > > > run
> >> > > > > > the migration soon. Again, Jira is still there, just
> read-only.
> >> > > > > >
> >> > > > > > Regards
> >> > > > > > JB
> >> > > > > >
> >> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> >> > > > > > dev@activemq.apache.org> wrote:
> >> > > > > >
> >> > > > > > > Nice!
> >> > > > > > >
> >> > > > > > > Will all old Jira issues be migrated to GitHub too?
> >> > > > > > >
> >> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
> >> would
> >> > > hate
> >> > > > > to
> >> > > > > > > see those bots automatically closing issues if they are
> >> > > "inactive". I
> >> > > > > > > understand that sometimes there is a need to manage a
> backlog,
> >> > but
> >> > > > this
> >> > > > > > > doesn't allow "voting" on issues with likes or other means
> of
> >> > > > activity
> >> > > > > > > other than "me too, please reopen" comments.
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > > Best Regards,
> >> > > > > > > Vilius
> >> > > > > > >
> >> > > > > > > -----Original Message-----
> >> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
> >> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> >> > > > > > > Subject: GitHub Issues & Discussions enabled
> >> > > > > > >
> >> > > > > > > Hi folks,
> >> > > > > > >
> >> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
> >> > > > > > >
> >> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues
> )
> >> > > > > > > Jira is now read-only and we should now all use GitHub
> Issues.
> >> > > > > > >
> >> > > > > > > We have the following labels available:
> >> > > > > > > - bug: for bug reports
> >> > > > > > > - dependencies: for dependencies updates
> >> > > > > > > - enhancement: for improvements on existing code
> >> > > > > > > - feature: for a complete new features
> >> > > > > > > - proposal: for a design proposal, big features
> >> > > > > > > - stale: when the issue is "inactive" for more than 60 days
> >> > > > > > >
> >> > > > > > > Please use these labels to classify the issues.
> >> > > > > > >
> >> > > > > > > When you create a PR, you can associate it with an issue
> >> either
> >> > in
> >> > > > the
> >> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
> >> > > > > > > I also suggest using conventional commit messages in PR with
> >> the
> >> > > > format
> >> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
> >> can
> >> > > be:
> >> > > > > > > - feat: (a new feature is introduced with the changes)
> >> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
> >> > > > > > > - docs: (changes to the documentation)
> >> > > > > > > - style: (formatting, missing semicolons, etc; no production
> >> code
> >> > > > > change)
> >> > > > > > > - refactor: (refactoring production code, eg. renaming a
> >> > variable)
> >> > > > > > > - test: (adding missing tests, refactoring tests; no
> >> production
> >> > > code
> >> > > > > > > change)
> >> > > > > > > - chore: (changes that do not relate to a fix or feature and
> >> > don't
> >> > > > > modify
> >> > > > > > > src or test files (for example updating dependencies or
> >> change in
> >> > > > > > > production code))
> >> > > > > > > - perf – (performance improvements)
> >> > > > > > > - ci – (continuous integration related)
> >> > > > > > > - build – (changes that affect the build system or external
> >> > > > > dependencies)
> >> > > > > > > - revert – (reverts a previous commit)
> >> > > > > > > That's a nice practice because GitHub can use that to create
> >> nice
> >> > > > > Release
> >> > > > > > > Notes.
> >> > > > > > > Thanks to that, it's not necessary to create GH issues for
> all
> >> > > > changes.
> >> > > > > > >
> >> > > > > > > For versions, we are using GitHub Projects (
> >> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen
> ).
> >> > > > > > > You can assign several projects/versions per issue, and
> track
> >> the
> >> > > > > status
> >> > > > > > > of the versions.
> >> > > > > > >
> >> > > > > > > 2. GitHub Discussions
> >> > > > > > > We also enabled GitHub Discussions where we can have
> technical
> >> > > > > > discussions.
> >> > > > > > > The GH Discussions are automatically going to the dev@
> >> mailing
> >> > > list.
> >> > > > > > >
> >> > > > > > > Let us know if you have any questions.
> >> > > > > > >
> >> > > > > > > Regards
> >> > > > > > > JB
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
I've enabled issues and discussions on the other repositories. Can we mark
jira for dotnet activemq components readonly the same way you marked
activemq?
Thanks,
KP
On Mon, May 11, 2026 at 5:25 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> GitHub Issues (and discussions) are now available for activemq-nms-api
> repo: https://github.com/apache/activemq-nms-api/issues
>
> I will create the PRs on https://github.com/apache/activemq-nms-amqp and
> https://github.com/apache/activemq-nms-openwire repositories.
>
> Regards
> JB
>
> On Mon, May 11, 2026 at 5:20 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > I went ahead and fixed the typo (missing space after :) on discussions.
> >
> > Regards
> > JB
> >
> > On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
> >
> >> JB, I think we need some adjustments:
> >>
> >> while scanning a simple key
> >> in "<byte string>", line 37, column 5:
> >> discussions:true
> >> ^
> >> could not find expected ':'
> >> in "<byte string>", line 39, column 1:
> >> notifications:
> >> ^
> >>
> >>
> >> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> wrote:
> >>
> >> > Hi
> >> >
> >> > I created a first PR for nms-api repo:
> >> > https://github.com/apache/activemq-nms-api/pull/35
> >> >
> >> > If it works for you, I will create the PRs for the other repos.
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
> >> >
> >> > > Hi JB,
> >> > >
> >> > > Any update on this? Or any action needed from my end?
> >> > >
> >> > > Best,
> >> > > KP
> >> > >
> >> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <
> jb@nanthrax.net
> >> >
> >> > > wrote:
> >> > >
> >> > > > Hi
> >> > > >
> >> > > > Sure, let me create the PRs for your review.
> >> > > >
> >> > > > Regards
> >> > > > JB
> >> > > >
> >> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org>
> wrote:
> >> > > >
> >> > > > > Hi JB,
> >> > > > >
> >> > > > > Could you walk me through the process of enabling github issues
> >> for:
> >> > > > >
> >> > > > > - https://github.com/apache/activemq-nms-api
> >> > > > > - https://github.com/apache/activemq-nms-amqp
> >> > > > > - https://github.com/apache/activemq-nms-openwire
> >> > > > >
> >> > > > > Thanks,
> >> > > > > KP
> >> > > > >
> >> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
> >> > jb@nanthrax.net>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Hi
> >> > > > > >
> >> > > > > > 1. About stale: the stale issues are flagged by not closed
> (only
> >> > the
> >> > > PR
> >> > > > > > could be closed by the stale bot). So the issues are still
> open
> >> > (just
> >> > > > > > flagged).
> >> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
> >> Jira
> >> > > > > tickets
> >> > > > > > to GH Issues. I'm creating issues manually for now (new
> >> issues). I
> >> > > will
> >> > > > > run
> >> > > > > > the migration soon. Again, Jira is still there, just
> read-only.
> >> > > > > >
> >> > > > > > Regards
> >> > > > > > JB
> >> > > > > >
> >> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> >> > > > > > dev@activemq.apache.org> wrote:
> >> > > > > >
> >> > > > > > > Nice!
> >> > > > > > >
> >> > > > > > > Will all old Jira issues be migrated to GitHub too?
> >> > > > > > >
> >> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
> >> would
> >> > > hate
> >> > > > > to
> >> > > > > > > see those bots automatically closing issues if they are
> >> > > "inactive". I
> >> > > > > > > understand that sometimes there is a need to manage a
> backlog,
> >> > but
> >> > > > this
> >> > > > > > > doesn't allow "voting" on issues with likes or other means
> of
> >> > > > activity
> >> > > > > > > other than "me too, please reopen" comments.
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > > Best Regards,
> >> > > > > > > Vilius
> >> > > > > > >
> >> > > > > > > -----Original Message-----
> >> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> >> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
> >> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> >> > > > > > > Subject: GitHub Issues & Discussions enabled
> >> > > > > > >
> >> > > > > > > Hi folks,
> >> > > > > > >
> >> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
> >> > > > > > >
> >> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues
> )
> >> > > > > > > Jira is now read-only and we should now all use GitHub
> Issues.
> >> > > > > > >
> >> > > > > > > We have the following labels available:
> >> > > > > > > - bug: for bug reports
> >> > > > > > > - dependencies: for dependencies updates
> >> > > > > > > - enhancement: for improvements on existing code
> >> > > > > > > - feature: for a complete new features
> >> > > > > > > - proposal: for a design proposal, big features
> >> > > > > > > - stale: when the issue is "inactive" for more than 60 days
> >> > > > > > >
> >> > > > > > > Please use these labels to classify the issues.
> >> > > > > > >
> >> > > > > > > When you create a PR, you can associate it with an issue
> >> either
> >> > in
> >> > > > the
> >> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
> >> > > > > > > I also suggest using conventional commit messages in PR with
> >> the
> >> > > > format
> >> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
> >> can
> >> > > be:
> >> > > > > > > - feat: (a new feature is introduced with the changes)
> >> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
> >> > > > > > > - docs: (changes to the documentation)
> >> > > > > > > - style: (formatting, missing semicolons, etc; no production
> >> code
> >> > > > > change)
> >> > > > > > > - refactor: (refactoring production code, eg. renaming a
> >> > variable)
> >> > > > > > > - test: (adding missing tests, refactoring tests; no
> >> production
> >> > > code
> >> > > > > > > change)
> >> > > > > > > - chore: (changes that do not relate to a fix or feature and
> >> > don't
> >> > > > > modify
> >> > > > > > > src or test files (for example updating dependencies or
> >> change in
> >> > > > > > > production code))
> >> > > > > > > - perf – (performance improvements)
> >> > > > > > > - ci – (continuous integration related)
> >> > > > > > > - build – (changes that affect the build system or external
> >> > > > > dependencies)
> >> > > > > > > - revert – (reverts a previous commit)
> >> > > > > > > That's a nice practice because GitHub can use that to create
> >> nice
> >> > > > > Release
> >> > > > > > > Notes.
> >> > > > > > > Thanks to that, it's not necessary to create GH issues for
> all
> >> > > > changes.
> >> > > > > > >
> >> > > > > > > For versions, we are using GitHub Projects (
> >> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen
> ).
> >> > > > > > > You can assign several projects/versions per issue, and
> track
> >> the
> >> > > > > status
> >> > > > > > > of the versions.
> >> > > > > > >
> >> > > > > > > 2. GitHub Discussions
> >> > > > > > > We also enabled GitHub Discussions where we can have
> technical
> >> > > > > > discussions.
> >> > > > > > > The GH Discussions are automatically going to the dev@
> >> mailing
> >> > > list.
> >> > > > > > >
> >> > > > > > > Let us know if you have any questions.
> >> > > > > > >
> >> > > > > > > Regards
> >> > > > > > > JB
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
GitHub Issues (and discussions) are now available for activemq-nms-api
repo: https://github.com/apache/activemq-nms-api/issues
I will create the PRs on https://github.com/apache/activemq-nms-amqp and
https://github.com/apache/activemq-nms-openwire repositories.
Regards
JB
On Mon, May 11, 2026 at 5:20 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> I went ahead and fixed the typo (missing space after :) on discussions.
>
> Regards
> JB
>
> On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
>
>> JB, I think we need some adjustments:
>>
>> while scanning a simple key
>> in "<byte string>", line 37, column 5:
>> discussions:true
>> ^
>> could not find expected ':'
>> in "<byte string>", line 39, column 1:
>> notifications:
>> ^
>>
>>
>> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>> > Hi
>> >
>> > I created a first PR for nms-api repo:
>> > https://github.com/apache/activemq-nms-api/pull/35
>> >
>> > If it works for you, I will create the PRs for the other repos.
>> >
>> > Regards
>> > JB
>> >
>> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
>> >
>> > > Hi JB,
>> > >
>> > > Any update on this? Or any action needed from my end?
>> > >
>> > > Best,
>> > > KP
>> > >
>> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb@nanthrax.net
>> >
>> > > wrote:
>> > >
>> > > > Hi
>> > > >
>> > > > Sure, let me create the PRs for your review.
>> > > >
>> > > > Regards
>> > > > JB
>> > > >
>> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
>> > > >
>> > > > > Hi JB,
>> > > > >
>> > > > > Could you walk me through the process of enabling github issues
>> for:
>> > > > >
>> > > > > - https://github.com/apache/activemq-nms-api
>> > > > > - https://github.com/apache/activemq-nms-amqp
>> > > > > - https://github.com/apache/activemq-nms-openwire
>> > > > >
>> > > > > Thanks,
>> > > > > KP
>> > > > >
>> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
>> > jb@nanthrax.net>
>> > > > > wrote:
>> > > > >
>> > > > > > Hi
>> > > > > >
>> > > > > > 1. About stale: the stale issues are flagged by not closed (only
>> > the
>> > > PR
>> > > > > > could be closed by the stale bot). So the issues are still open
>> > (just
>> > > > > > flagged).
>> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
>> Jira
>> > > > > tickets
>> > > > > > to GH Issues. I'm creating issues manually for now (new
>> issues). I
>> > > will
>> > > > > run
>> > > > > > the migration soon. Again, Jira is still there, just read-only.
>> > > > > >
>> > > > > > Regards
>> > > > > > JB
>> > > > > >
>> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
>> > > > > > dev@activemq.apache.org> wrote:
>> > > > > >
>> > > > > > > Nice!
>> > > > > > >
>> > > > > > > Will all old Jira issues be migrated to GitHub too?
>> > > > > > >
>> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
>> would
>> > > hate
>> > > > > to
>> > > > > > > see those bots automatically closing issues if they are
>> > > "inactive". I
>> > > > > > > understand that sometimes there is a need to manage a backlog,
>> > but
>> > > > this
>> > > > > > > doesn't allow "voting" on issues with likes or other means of
>> > > > activity
>> > > > > > > other than "me too, please reopen" comments.
>> > > > > > >
>> > > > > > > --
>> > > > > > > Best Regards,
>> > > > > > > Vilius
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
>> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
>> > > > > > > Subject: GitHub Issues & Discussions enabled
>> > > > > > >
>> > > > > > > Hi folks,
>> > > > > > >
>> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
>> > > > > > >
>> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
>> > > > > > > Jira is now read-only and we should now all use GitHub Issues.
>> > > > > > >
>> > > > > > > We have the following labels available:
>> > > > > > > - bug: for bug reports
>> > > > > > > - dependencies: for dependencies updates
>> > > > > > > - enhancement: for improvements on existing code
>> > > > > > > - feature: for a complete new features
>> > > > > > > - proposal: for a design proposal, big features
>> > > > > > > - stale: when the issue is "inactive" for more than 60 days
>> > > > > > >
>> > > > > > > Please use these labels to classify the issues.
>> > > > > > >
>> > > > > > > When you create a PR, you can associate it with an issue
>> either
>> > in
>> > > > the
>> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
>> > > > > > > I also suggest using conventional commit messages in PR with
>> the
>> > > > format
>> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
>> can
>> > > be:
>> > > > > > > - feat: (a new feature is introduced with the changes)
>> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
>> > > > > > > - docs: (changes to the documentation)
>> > > > > > > - style: (formatting, missing semicolons, etc; no production
>> code
>> > > > > change)
>> > > > > > > - refactor: (refactoring production code, eg. renaming a
>> > variable)
>> > > > > > > - test: (adding missing tests, refactoring tests; no
>> production
>> > > code
>> > > > > > > change)
>> > > > > > > - chore: (changes that do not relate to a fix or feature and
>> > don't
>> > > > > modify
>> > > > > > > src or test files (for example updating dependencies or
>> change in
>> > > > > > > production code))
>> > > > > > > - perf – (performance improvements)
>> > > > > > > - ci – (continuous integration related)
>> > > > > > > - build – (changes that affect the build system or external
>> > > > > dependencies)
>> > > > > > > - revert – (reverts a previous commit)
>> > > > > > > That's a nice practice because GitHub can use that to create
>> nice
>> > > > > Release
>> > > > > > > Notes.
>> > > > > > > Thanks to that, it's not necessary to create GH issues for all
>> > > > changes.
>> > > > > > >
>> > > > > > > For versions, we are using GitHub Projects (
>> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
>> > > > > > > You can assign several projects/versions per issue, and track
>> the
>> > > > > status
>> > > > > > > of the versions.
>> > > > > > >
>> > > > > > > 2. GitHub Discussions
>> > > > > > > We also enabled GitHub Discussions where we can have technical
>> > > > > > discussions.
>> > > > > > > The GH Discussions are automatically going to the dev@
>> mailing
>> > > list.
>> > > > > > >
>> > > > > > > Let us know if you have any questions.
>> > > > > > >
>> > > > > > > Regards
>> > > > > > > JB
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
GitHub Issues (and discussions) are now available for activemq-nms-api
repo: https://github.com/apache/activemq-nms-api/issues
I will create the PRs on https://github.com/apache/activemq-nms-amqp and
https://github.com/apache/activemq-nms-openwire repositories.
Regards
JB
On Mon, May 11, 2026 at 5:20 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> I went ahead and fixed the typo (missing space after :) on discussions.
>
> Regards
> JB
>
> On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
>
>> JB, I think we need some adjustments:
>>
>> while scanning a simple key
>> in "<byte string>", line 37, column 5:
>> discussions:true
>> ^
>> could not find expected ':'
>> in "<byte string>", line 39, column 1:
>> notifications:
>> ^
>>
>>
>> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>> > Hi
>> >
>> > I created a first PR for nms-api repo:
>> > https://github.com/apache/activemq-nms-api/pull/35
>> >
>> > If it works for you, I will create the PRs for the other repos.
>> >
>> > Regards
>> > JB
>> >
>> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
>> >
>> > > Hi JB,
>> > >
>> > > Any update on this? Or any action needed from my end?
>> > >
>> > > Best,
>> > > KP
>> > >
>> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb@nanthrax.net
>> >
>> > > wrote:
>> > >
>> > > > Hi
>> > > >
>> > > > Sure, let me create the PRs for your review.
>> > > >
>> > > > Regards
>> > > > JB
>> > > >
>> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
>> > > >
>> > > > > Hi JB,
>> > > > >
>> > > > > Could you walk me through the process of enabling github issues
>> for:
>> > > > >
>> > > > > - https://github.com/apache/activemq-nms-api
>> > > > > - https://github.com/apache/activemq-nms-amqp
>> > > > > - https://github.com/apache/activemq-nms-openwire
>> > > > >
>> > > > > Thanks,
>> > > > > KP
>> > > > >
>> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
>> > jb@nanthrax.net>
>> > > > > wrote:
>> > > > >
>> > > > > > Hi
>> > > > > >
>> > > > > > 1. About stale: the stale issues are flagged by not closed (only
>> > the
>> > > PR
>> > > > > > could be closed by the stale bot). So the issues are still open
>> > (just
>> > > > > > flagged).
>> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
>> Jira
>> > > > > tickets
>> > > > > > to GH Issues. I'm creating issues manually for now (new
>> issues). I
>> > > will
>> > > > > run
>> > > > > > the migration soon. Again, Jira is still there, just read-only.
>> > > > > >
>> > > > > > Regards
>> > > > > > JB
>> > > > > >
>> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
>> > > > > > dev@activemq.apache.org> wrote:
>> > > > > >
>> > > > > > > Nice!
>> > > > > > >
>> > > > > > > Will all old Jira issues be migrated to GitHub too?
>> > > > > > >
>> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
>> would
>> > > hate
>> > > > > to
>> > > > > > > see those bots automatically closing issues if they are
>> > > "inactive". I
>> > > > > > > understand that sometimes there is a need to manage a backlog,
>> > but
>> > > > this
>> > > > > > > doesn't allow "voting" on issues with likes or other means of
>> > > > activity
>> > > > > > > other than "me too, please reopen" comments.
>> > > > > > >
>> > > > > > > --
>> > > > > > > Best Regards,
>> > > > > > > Vilius
>> > > > > > >
>> > > > > > > -----Original Message-----
>> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
>> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
>> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
>> > > > > > > Subject: GitHub Issues & Discussions enabled
>> > > > > > >
>> > > > > > > Hi folks,
>> > > > > > >
>> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
>> > > > > > >
>> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
>> > > > > > > Jira is now read-only and we should now all use GitHub Issues.
>> > > > > > >
>> > > > > > > We have the following labels available:
>> > > > > > > - bug: for bug reports
>> > > > > > > - dependencies: for dependencies updates
>> > > > > > > - enhancement: for improvements on existing code
>> > > > > > > - feature: for a complete new features
>> > > > > > > - proposal: for a design proposal, big features
>> > > > > > > - stale: when the issue is "inactive" for more than 60 days
>> > > > > > >
>> > > > > > > Please use these labels to classify the issues.
>> > > > > > >
>> > > > > > > When you create a PR, you can associate it with an issue
>> either
>> > in
>> > > > the
>> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
>> > > > > > > I also suggest using conventional commit messages in PR with
>> the
>> > > > format
>> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
>> can
>> > > be:
>> > > > > > > - feat: (a new feature is introduced with the changes)
>> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
>> > > > > > > - docs: (changes to the documentation)
>> > > > > > > - style: (formatting, missing semicolons, etc; no production
>> code
>> > > > > change)
>> > > > > > > - refactor: (refactoring production code, eg. renaming a
>> > variable)
>> > > > > > > - test: (adding missing tests, refactoring tests; no
>> production
>> > > code
>> > > > > > > change)
>> > > > > > > - chore: (changes that do not relate to a fix or feature and
>> > don't
>> > > > > modify
>> > > > > > > src or test files (for example updating dependencies or
>> change in
>> > > > > > > production code))
>> > > > > > > - perf – (performance improvements)
>> > > > > > > - ci – (continuous integration related)
>> > > > > > > - build – (changes that affect the build system or external
>> > > > > dependencies)
>> > > > > > > - revert – (reverts a previous commit)
>> > > > > > > That's a nice practice because GitHub can use that to create
>> nice
>> > > > > Release
>> > > > > > > Notes.
>> > > > > > > Thanks to that, it's not necessary to create GH issues for all
>> > > > changes.
>> > > > > > >
>> > > > > > > For versions, we are using GitHub Projects (
>> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
>> > > > > > > You can assign several projects/versions per issue, and track
>> the
>> > > > > status
>> > > > > > > of the versions.
>> > > > > > >
>> > > > > > > 2. GitHub Discussions
>> > > > > > > We also enabled GitHub Discussions where we can have technical
>> > > > > > discussions.
>> > > > > > > The GH Discussions are automatically going to the dev@
>> mailing
>> > > list.
>> > > > > > >
>> > > > > > > Let us know if you have any questions.
>> > > > > > >
>> > > > > > > Regards
>> > > > > > > JB
>> > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
I went ahead and fixed the typo (missing space after :) on discussions.
Regards
JB
On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
> JB, I think we need some adjustments:
>
> while scanning a simple key
> in "<byte string>", line 37, column 5:
> discussions:true
> ^
> could not find expected ':'
> in "<byte string>", line 39, column 1:
> notifications:
> ^
>
>
> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > I created a first PR for nms-api repo:
> > https://github.com/apache/activemq-nms-api/pull/35
> >
> > If it works for you, I will create the PRs for the other repos.
> >
> > Regards
> > JB
> >
> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
> >
> > > Hi JB,
> > >
> > > Any update on this? Or any action needed from my end?
> > >
> > > Best,
> > > KP
> > >
> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > Sure, let me create the PRs for your review.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> > > >
> > > > > Hi JB,
> > > > >
> > > > > Could you walk me through the process of enabling github issues
> for:
> > > > >
> > > > > - https://github.com/apache/activemq-nms-api
> > > > > - https://github.com/apache/activemq-nms-amqp
> > > > > - https://github.com/apache/activemq-nms-openwire
> > > > >
> > > > > Thanks,
> > > > > KP
> > > > >
> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
> > jb@nanthrax.net>
> > > > > wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > 1. About stale: the stale issues are flagged by not closed (only
> > the
> > > PR
> > > > > > could be closed by the stale bot). So the issues are still open
> > (just
> > > > > > flagged).
> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
> Jira
> > > > > tickets
> > > > > > to GH Issues. I'm creating issues manually for now (new issues).
> I
> > > will
> > > > > run
> > > > > > the migration soon. Again, Jira is still there, just read-only.
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > > > > dev@activemq.apache.org> wrote:
> > > > > >
> > > > > > > Nice!
> > > > > > >
> > > > > > > Will all old Jira issues be migrated to GitHub too?
> > > > > > >
> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
> would
> > > hate
> > > > > to
> > > > > > > see those bots automatically closing issues if they are
> > > "inactive". I
> > > > > > > understand that sometimes there is a need to manage a backlog,
> > but
> > > > this
> > > > > > > doesn't allow "voting" on issues with likes or other means of
> > > > activity
> > > > > > > other than "me too, please reopen" comments.
> > > > > > >
> > > > > > > --
> > > > > > > Best Regards,
> > > > > > > Vilius
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > > > > Subject: GitHub Issues & Discussions enabled
> > > > > > >
> > > > > > > Hi folks,
> > > > > > >
> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > > > >
> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > > > >
> > > > > > > We have the following labels available:
> > > > > > > - bug: for bug reports
> > > > > > > - dependencies: for dependencies updates
> > > > > > > - enhancement: for improvements on existing code
> > > > > > > - feature: for a complete new features
> > > > > > > - proposal: for a design proposal, big features
> > > > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > > > >
> > > > > > > Please use these labels to classify the issues.
> > > > > > >
> > > > > > > When you create a PR, you can associate it with an issue either
> > in
> > > > the
> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > > > I also suggest using conventional commit messages in PR with
> the
> > > > format
> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
> can
> > > be:
> > > > > > > - feat: (a new feature is introduced with the changes)
> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > > > - docs: (changes to the documentation)
> > > > > > > - style: (formatting, missing semicolons, etc; no production
> code
> > > > > change)
> > > > > > > - refactor: (refactoring production code, eg. renaming a
> > variable)
> > > > > > > - test: (adding missing tests, refactoring tests; no production
> > > code
> > > > > > > change)
> > > > > > > - chore: (changes that do not relate to a fix or feature and
> > don't
> > > > > modify
> > > > > > > src or test files (for example updating dependencies or change
> in
> > > > > > > production code))
> > > > > > > - perf – (performance improvements)
> > > > > > > - ci – (continuous integration related)
> > > > > > > - build – (changes that affect the build system or external
> > > > > dependencies)
> > > > > > > - revert – (reverts a previous commit)
> > > > > > > That's a nice practice because GitHub can use that to create
> nice
> > > > > Release
> > > > > > > Notes.
> > > > > > > Thanks to that, it's not necessary to create GH issues for all
> > > > changes.
> > > > > > >
> > > > > > > For versions, we are using GitHub Projects (
> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > > > You can assign several projects/versions per issue, and track
> the
> > > > > status
> > > > > > > of the versions.
> > > > > > >
> > > > > > > 2. GitHub Discussions
> > > > > > > We also enabled GitHub Discussions where we can have technical
> > > > > > discussions.
> > > > > > > The GH Discussions are automatically going to the dev@ mailing
> > > list.
> > > > > > >
> > > > > > > Let us know if you have any questions.
> > > > > > >
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
I went ahead and fixed the typo (missing space after :) on discussions.
Regards
JB
On Sun, May 10, 2026 at 6:50 PM Havret <ha...@apache.org> wrote:
> JB, I think we need some adjustments:
>
> while scanning a simple key
> in "<byte string>", line 37, column 5:
> discussions:true
> ^
> could not find expected ':'
> in "<byte string>", line 39, column 1:
> notifications:
> ^
>
>
> On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > I created a first PR for nms-api repo:
> > https://github.com/apache/activemq-nms-api/pull/35
> >
> > If it works for you, I will create the PRs for the other repos.
> >
> > Regards
> > JB
> >
> > On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
> >
> > > Hi JB,
> > >
> > > Any update on this? Or any action needed from my end?
> > >
> > > Best,
> > > KP
> > >
> > > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > Sure, let me create the PRs for your review.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> > > >
> > > > > Hi JB,
> > > > >
> > > > > Could you walk me through the process of enabling github issues
> for:
> > > > >
> > > > > - https://github.com/apache/activemq-nms-api
> > > > > - https://github.com/apache/activemq-nms-amqp
> > > > > - https://github.com/apache/activemq-nms-openwire
> > > > >
> > > > > Thanks,
> > > > > KP
> > > > >
> > > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
> > jb@nanthrax.net>
> > > > > wrote:
> > > > >
> > > > > > Hi
> > > > > >
> > > > > > 1. About stale: the stale issues are flagged by not closed (only
> > the
> > > PR
> > > > > > could be closed by the stale bot). So the issues are still open
> > (just
> > > > > > flagged).
> > > > > > 2. Yes, we have a script provided by the ASF infra to migrate
> Jira
> > > > > tickets
> > > > > > to GH Issues. I'm creating issues manually for now (new issues).
> I
> > > will
> > > > > run
> > > > > > the migration soon. Again, Jira is still there, just read-only.
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > > > > dev@activemq.apache.org> wrote:
> > > > > >
> > > > > > > Nice!
> > > > > > >
> > > > > > > Will all old Jira issues be migrated to GitHub too?
> > > > > > >
> > > > > > > Also, I'm wondering, how "stale" issues will be managed? I
> would
> > > hate
> > > > > to
> > > > > > > see those bots automatically closing issues if they are
> > > "inactive". I
> > > > > > > understand that sometimes there is a need to manage a backlog,
> > but
> > > > this
> > > > > > > doesn't allow "voting" on issues with likes or other means of
> > > > activity
> > > > > > > other than "me too, please reopen" comments.
> > > > > > >
> > > > > > > --
> > > > > > > Best Regards,
> > > > > > > Vilius
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > > > > Subject: GitHub Issues & Discussions enabled
> > > > > > >
> > > > > > > Hi folks,
> > > > > > >
> > > > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > > > >
> > > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > > > >
> > > > > > > We have the following labels available:
> > > > > > > - bug: for bug reports
> > > > > > > - dependencies: for dependencies updates
> > > > > > > - enhancement: for improvements on existing code
> > > > > > > - feature: for a complete new features
> > > > > > > - proposal: for a design proposal, big features
> > > > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > > > >
> > > > > > > Please use these labels to classify the issues.
> > > > > > >
> > > > > > > When you create a PR, you can associate it with an issue either
> > in
> > > > the
> > > > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > > > I also suggest using conventional commit messages in PR with
> the
> > > > format
> > > > > > > <type>(<scope>): <subject> where scope is optional. The type
> can
> > > be:
> > > > > > > - feat: (a new feature is introduced with the changes)
> > > > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > > > - docs: (changes to the documentation)
> > > > > > > - style: (formatting, missing semicolons, etc; no production
> code
> > > > > change)
> > > > > > > - refactor: (refactoring production code, eg. renaming a
> > variable)
> > > > > > > - test: (adding missing tests, refactoring tests; no production
> > > code
> > > > > > > change)
> > > > > > > - chore: (changes that do not relate to a fix or feature and
> > don't
> > > > > modify
> > > > > > > src or test files (for example updating dependencies or change
> in
> > > > > > > production code))
> > > > > > > - perf – (performance improvements)
> > > > > > > - ci – (continuous integration related)
> > > > > > > - build – (changes that affect the build system or external
> > > > > dependencies)
> > > > > > > - revert – (reverts a previous commit)
> > > > > > > That's a nice practice because GitHub can use that to create
> nice
> > > > > Release
> > > > > > > Notes.
> > > > > > > Thanks to that, it's not necessary to create GH issues for all
> > > > changes.
> > > > > > >
> > > > > > > For versions, we are using GitHub Projects (
> > > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > > > You can assign several projects/versions per issue, and track
> the
> > > > > status
> > > > > > > of the versions.
> > > > > > >
> > > > > > > 2. GitHub Discussions
> > > > > > > We also enabled GitHub Discussions where we can have technical
> > > > > > discussions.
> > > > > > > The GH Discussions are automatically going to the dev@ mailing
> > > list.
> > > > > > >
> > > > > > > Let us know if you have any questions.
> > > > > > >
> > > > > > > Regards
> > > > > > > JB
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
JB, I think we need some adjustments:
while scanning a simple key
in "<byte string>", line 37, column 5:
discussions:true
^
could not find expected ':'
in "<byte string>", line 39, column 1:
notifications:
^
On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> I created a first PR for nms-api repo:
> https://github.com/apache/activemq-nms-api/pull/35
>
> If it works for you, I will create the PRs for the other repos.
>
> Regards
> JB
>
> On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
>
> > Hi JB,
> >
> > Any update on this? Or any action needed from my end?
> >
> > Best,
> > KP
> >
> > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi
> > >
> > > Sure, let me create the PRs for your review.
> > >
> > > Regards
> > > JB
> > >
> > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> > >
> > > > Hi JB,
> > > >
> > > > Could you walk me through the process of enabling github issues for:
> > > >
> > > > - https://github.com/apache/activemq-nms-api
> > > > - https://github.com/apache/activemq-nms-amqp
> > > > - https://github.com/apache/activemq-nms-openwire
> > > >
> > > > Thanks,
> > > > KP
> > > >
> > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
> jb@nanthrax.net>
> > > > wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > 1. About stale: the stale issues are flagged by not closed (only
> the
> > PR
> > > > > could be closed by the stale bot). So the issues are still open
> (just
> > > > > flagged).
> > > > > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> > > > tickets
> > > > > to GH Issues. I'm creating issues manually for now (new issues). I
> > will
> > > > run
> > > > > the migration soon. Again, Jira is still there, just read-only.
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > > > dev@activemq.apache.org> wrote:
> > > > >
> > > > > > Nice!
> > > > > >
> > > > > > Will all old Jira issues be migrated to GitHub too?
> > > > > >
> > > > > > Also, I'm wondering, how "stale" issues will be managed? I would
> > hate
> > > > to
> > > > > > see those bots automatically closing issues if they are
> > "inactive". I
> > > > > > understand that sometimes there is a need to manage a backlog,
> but
> > > this
> > > > > > doesn't allow "voting" on issues with likes or other means of
> > > activity
> > > > > > other than "me too, please reopen" comments.
> > > > > >
> > > > > > --
> > > > > > Best Regards,
> > > > > > Vilius
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > > > Subject: GitHub Issues & Discussions enabled
> > > > > >
> > > > > > Hi folks,
> > > > > >
> > > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > > >
> > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > > >
> > > > > > We have the following labels available:
> > > > > > - bug: for bug reports
> > > > > > - dependencies: for dependencies updates
> > > > > > - enhancement: for improvements on existing code
> > > > > > - feature: for a complete new features
> > > > > > - proposal: for a design proposal, big features
> > > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > > >
> > > > > > Please use these labels to classify the issues.
> > > > > >
> > > > > > When you create a PR, you can associate it with an issue either
> in
> > > the
> > > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > > I also suggest using conventional commit messages in PR with the
> > > format
> > > > > > <type>(<scope>): <subject> where scope is optional. The type can
> > be:
> > > > > > - feat: (a new feature is introduced with the changes)
> > > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > > - docs: (changes to the documentation)
> > > > > > - style: (formatting, missing semicolons, etc; no production code
> > > > change)
> > > > > > - refactor: (refactoring production code, eg. renaming a
> variable)
> > > > > > - test: (adding missing tests, refactoring tests; no production
> > code
> > > > > > change)
> > > > > > - chore: (changes that do not relate to a fix or feature and
> don't
> > > > modify
> > > > > > src or test files (for example updating dependencies or change in
> > > > > > production code))
> > > > > > - perf – (performance improvements)
> > > > > > - ci – (continuous integration related)
> > > > > > - build – (changes that affect the build system or external
> > > > dependencies)
> > > > > > - revert – (reverts a previous commit)
> > > > > > That's a nice practice because GitHub can use that to create nice
> > > > Release
> > > > > > Notes.
> > > > > > Thanks to that, it's not necessary to create GH issues for all
> > > changes.
> > > > > >
> > > > > > For versions, we are using GitHub Projects (
> > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > > You can assign several projects/versions per issue, and track the
> > > > status
> > > > > > of the versions.
> > > > > >
> > > > > > 2. GitHub Discussions
> > > > > > We also enabled GitHub Discussions where we can have technical
> > > > > discussions.
> > > > > > The GH Discussions are automatically going to the dev@ mailing
> > list.
> > > > > >
> > > > > > Let us know if you have any questions.
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
JB, I think we need some adjustments:
while scanning a simple key
in "<byte string>", line 37, column 5:
discussions:true
^
could not find expected ':'
in "<byte string>", line 39, column 1:
notifications:
^
On Sun, May 10, 2026 at 4:58 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> I created a first PR for nms-api repo:
> https://github.com/apache/activemq-nms-api/pull/35
>
> If it works for you, I will create the PRs for the other repos.
>
> Regards
> JB
>
> On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
>
> > Hi JB,
> >
> > Any update on this? Or any action needed from my end?
> >
> > Best,
> > KP
> >
> > On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi
> > >
> > > Sure, let me create the PRs for your review.
> > >
> > > Regards
> > > JB
> > >
> > > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> > >
> > > > Hi JB,
> > > >
> > > > Could you walk me through the process of enabling github issues for:
> > > >
> > > > - https://github.com/apache/activemq-nms-api
> > > > - https://github.com/apache/activemq-nms-amqp
> > > > - https://github.com/apache/activemq-nms-openwire
> > > >
> > > > Thanks,
> > > > KP
> > > >
> > > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <
> jb@nanthrax.net>
> > > > wrote:
> > > >
> > > > > Hi
> > > > >
> > > > > 1. About stale: the stale issues are flagged by not closed (only
> the
> > PR
> > > > > could be closed by the stale bot). So the issues are still open
> (just
> > > > > flagged).
> > > > > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> > > > tickets
> > > > > to GH Issues. I'm creating issues manually for now (new issues). I
> > will
> > > > run
> > > > > the migration soon. Again, Jira is still there, just read-only.
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > > > dev@activemq.apache.org> wrote:
> > > > >
> > > > > > Nice!
> > > > > >
> > > > > > Will all old Jira issues be migrated to GitHub too?
> > > > > >
> > > > > > Also, I'm wondering, how "stale" issues will be managed? I would
> > hate
> > > > to
> > > > > > see those bots automatically closing issues if they are
> > "inactive". I
> > > > > > understand that sometimes there is a need to manage a backlog,
> but
> > > this
> > > > > > doesn't allow "voting" on issues with likes or other means of
> > > activity
> > > > > > other than "me too, please reopen" comments.
> > > > > >
> > > > > > --
> > > > > > Best Regards,
> > > > > > Vilius
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > > > Subject: GitHub Issues & Discussions enabled
> > > > > >
> > > > > > Hi folks,
> > > > > >
> > > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > > >
> > > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > > >
> > > > > > We have the following labels available:
> > > > > > - bug: for bug reports
> > > > > > - dependencies: for dependencies updates
> > > > > > - enhancement: for improvements on existing code
> > > > > > - feature: for a complete new features
> > > > > > - proposal: for a design proposal, big features
> > > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > > >
> > > > > > Please use these labels to classify the issues.
> > > > > >
> > > > > > When you create a PR, you can associate it with an issue either
> in
> > > the
> > > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > > I also suggest using conventional commit messages in PR with the
> > > format
> > > > > > <type>(<scope>): <subject> where scope is optional. The type can
> > be:
> > > > > > - feat: (a new feature is introduced with the changes)
> > > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > > - docs: (changes to the documentation)
> > > > > > - style: (formatting, missing semicolons, etc; no production code
> > > > change)
> > > > > > - refactor: (refactoring production code, eg. renaming a
> variable)
> > > > > > - test: (adding missing tests, refactoring tests; no production
> > code
> > > > > > change)
> > > > > > - chore: (changes that do not relate to a fix or feature and
> don't
> > > > modify
> > > > > > src or test files (for example updating dependencies or change in
> > > > > > production code))
> > > > > > - perf – (performance improvements)
> > > > > > - ci – (continuous integration related)
> > > > > > - build – (changes that affect the build system or external
> > > > dependencies)
> > > > > > - revert – (reverts a previous commit)
> > > > > > That's a nice practice because GitHub can use that to create nice
> > > > Release
> > > > > > Notes.
> > > > > > Thanks to that, it's not necessary to create GH issues for all
> > > changes.
> > > > > >
> > > > > > For versions, we are using GitHub Projects (
> > > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > > You can assign several projects/versions per issue, and track the
> > > > status
> > > > > > of the versions.
> > > > > >
> > > > > > 2. GitHub Discussions
> > > > > > We also enabled GitHub Discussions where we can have technical
> > > > > discussions.
> > > > > > The GH Discussions are automatically going to the dev@ mailing
> > list.
> > > > > >
> > > > > > Let us know if you have any questions.
> > > > > >
> > > > > > Regards
> > > > > > JB
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
I created a first PR for nms-api repo:
https://github.com/apache/activemq-nms-api/pull/35
If it works for you, I will create the PRs for the other repos.
Regards
JB
On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
> Hi JB,
>
> Any update on this? Or any action needed from my end?
>
> Best,
> KP
>
> On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > Sure, let me create the PRs for your review.
> >
> > Regards
> > JB
> >
> > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> >
> > > Hi JB,
> > >
> > > Could you walk me through the process of enabling github issues for:
> > >
> > > - https://github.com/apache/activemq-nms-api
> > > - https://github.com/apache/activemq-nms-amqp
> > > - https://github.com/apache/activemq-nms-openwire
> > >
> > > Thanks,
> > > KP
> > >
> > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > 1. About stale: the stale issues are flagged by not closed (only the
> PR
> > > > could be closed by the stale bot). So the issues are still open (just
> > > > flagged).
> > > > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> > > tickets
> > > > to GH Issues. I'm creating issues manually for now (new issues). I
> will
> > > run
> > > > the migration soon. Again, Jira is still there, just read-only.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > > dev@activemq.apache.org> wrote:
> > > >
> > > > > Nice!
> > > > >
> > > > > Will all old Jira issues be migrated to GitHub too?
> > > > >
> > > > > Also, I'm wondering, how "stale" issues will be managed? I would
> hate
> > > to
> > > > > see those bots automatically closing issues if they are
> "inactive". I
> > > > > understand that sometimes there is a need to manage a backlog, but
> > this
> > > > > doesn't allow "voting" on issues with likes or other means of
> > activity
> > > > > other than "me too, please reopen" comments.
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > Vilius
> > > > >
> > > > > -----Original Message-----
> > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > > Subject: GitHub Issues & Discussions enabled
> > > > >
> > > > > Hi folks,
> > > > >
> > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > >
> > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > >
> > > > > We have the following labels available:
> > > > > - bug: for bug reports
> > > > > - dependencies: for dependencies updates
> > > > > - enhancement: for improvements on existing code
> > > > > - feature: for a complete new features
> > > > > - proposal: for a design proposal, big features
> > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > >
> > > > > Please use these labels to classify the issues.
> > > > >
> > > > > When you create a PR, you can associate it with an issue either in
> > the
> > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > I also suggest using conventional commit messages in PR with the
> > format
> > > > > <type>(<scope>): <subject> where scope is optional. The type can
> be:
> > > > > - feat: (a new feature is introduced with the changes)
> > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > - docs: (changes to the documentation)
> > > > > - style: (formatting, missing semicolons, etc; no production code
> > > change)
> > > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > > - test: (adding missing tests, refactoring tests; no production
> code
> > > > > change)
> > > > > - chore: (changes that do not relate to a fix or feature and don't
> > > modify
> > > > > src or test files (for example updating dependencies or change in
> > > > > production code))
> > > > > - perf – (performance improvements)
> > > > > - ci – (continuous integration related)
> > > > > - build – (changes that affect the build system or external
> > > dependencies)
> > > > > - revert – (reverts a previous commit)
> > > > > That's a nice practice because GitHub can use that to create nice
> > > Release
> > > > > Notes.
> > > > > Thanks to that, it's not necessary to create GH issues for all
> > changes.
> > > > >
> > > > > For versions, we are using GitHub Projects (
> > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > You can assign several projects/versions per issue, and track the
> > > status
> > > > > of the versions.
> > > > >
> > > > > 2. GitHub Discussions
> > > > > We also enabled GitHub Discussions where we can have technical
> > > > discussions.
> > > > > The GH Discussions are automatically going to the dev@ mailing
> list.
> > > > >
> > > > > Let us know if you have any questions.
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
I created a first PR for nms-api repo:
https://github.com/apache/activemq-nms-api/pull/35
If it works for you, I will create the PRs for the other repos.
Regards
JB
On Sun, May 10, 2026 at 12:50 PM Havret <ha...@apache.org> wrote:
> Hi JB,
>
> Any update on this? Or any action needed from my end?
>
> Best,
> KP
>
> On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > Sure, let me create the PRs for your review.
> >
> > Regards
> > JB
> >
> > On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> >
> > > Hi JB,
> > >
> > > Could you walk me through the process of enabling github issues for:
> > >
> > > - https://github.com/apache/activemq-nms-api
> > > - https://github.com/apache/activemq-nms-amqp
> > > - https://github.com/apache/activemq-nms-openwire
> > >
> > > Thanks,
> > > KP
> > >
> > > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > >
> > > > Hi
> > > >
> > > > 1. About stale: the stale issues are flagged by not closed (only the
> PR
> > > > could be closed by the stale bot). So the issues are still open (just
> > > > flagged).
> > > > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> > > tickets
> > > > to GH Issues. I'm creating issues manually for now (new issues). I
> will
> > > run
> > > > the migration soon. Again, Jira is still there, just read-only.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > > dev@activemq.apache.org> wrote:
> > > >
> > > > > Nice!
> > > > >
> > > > > Will all old Jira issues be migrated to GitHub too?
> > > > >
> > > > > Also, I'm wondering, how "stale" issues will be managed? I would
> hate
> > > to
> > > > > see those bots automatically closing issues if they are
> "inactive". I
> > > > > understand that sometimes there is a need to manage a backlog, but
> > this
> > > > > doesn't allow "voting" on issues with likes or other means of
> > activity
> > > > > other than "me too, please reopen" comments.
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > Vilius
> > > > >
> > > > > -----Original Message-----
> > > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > > Subject: GitHub Issues & Discussions enabled
> > > > >
> > > > > Hi folks,
> > > > >
> > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > >
> > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > >
> > > > > We have the following labels available:
> > > > > - bug: for bug reports
> > > > > - dependencies: for dependencies updates
> > > > > - enhancement: for improvements on existing code
> > > > > - feature: for a complete new features
> > > > > - proposal: for a design proposal, big features
> > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > >
> > > > > Please use these labels to classify the issues.
> > > > >
> > > > > When you create a PR, you can associate it with an issue either in
> > the
> > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > I also suggest using conventional commit messages in PR with the
> > format
> > > > > <type>(<scope>): <subject> where scope is optional. The type can
> be:
> > > > > - feat: (a new feature is introduced with the changes)
> > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > - docs: (changes to the documentation)
> > > > > - style: (formatting, missing semicolons, etc; no production code
> > > change)
> > > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > > - test: (adding missing tests, refactoring tests; no production
> code
> > > > > change)
> > > > > - chore: (changes that do not relate to a fix or feature and don't
> > > modify
> > > > > src or test files (for example updating dependencies or change in
> > > > > production code))
> > > > > - perf – (performance improvements)
> > > > > - ci – (continuous integration related)
> > > > > - build – (changes that affect the build system or external
> > > dependencies)
> > > > > - revert – (reverts a previous commit)
> > > > > That's a nice practice because GitHub can use that to create nice
> > > Release
> > > > > Notes.
> > > > > Thanks to that, it's not necessary to create GH issues for all
> > changes.
> > > > >
> > > > > For versions, we are using GitHub Projects (
> > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > You can assign several projects/versions per issue, and track the
> > > status
> > > > > of the versions.
> > > > >
> > > > > 2. GitHub Discussions
> > > > > We also enabled GitHub Discussions where we can have technical
> > > > discussions.
> > > > > The GH Discussions are automatically going to the dev@ mailing
> list.
> > > > >
> > > > > Let us know if you have any questions.
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
Any update on this? Or any action needed from my end?
Best,
KP
On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> Sure, let me create the PRs for your review.
>
> Regards
> JB
>
> On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
>
> > Hi JB,
> >
> > Could you walk me through the process of enabling github issues for:
> >
> > - https://github.com/apache/activemq-nms-api
> > - https://github.com/apache/activemq-nms-amqp
> > - https://github.com/apache/activemq-nms-openwire
> >
> > Thanks,
> > KP
> >
> > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi
> > >
> > > 1. About stale: the stale issues are flagged by not closed (only the PR
> > > could be closed by the stale bot). So the issues are still open (just
> > > flagged).
> > > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> > tickets
> > > to GH Issues. I'm creating issues manually for now (new issues). I will
> > run
> > > the migration soon. Again, Jira is still there, just read-only.
> > >
> > > Regards
> > > JB
> > >
> > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > dev@activemq.apache.org> wrote:
> > >
> > > > Nice!
> > > >
> > > > Will all old Jira issues be migrated to GitHub too?
> > > >
> > > > Also, I'm wondering, how "stale" issues will be managed? I would hate
> > to
> > > > see those bots automatically closing issues if they are "inactive". I
> > > > understand that sometimes there is a need to manage a backlog, but
> this
> > > > doesn't allow "voting" on issues with likes or other means of
> activity
> > > > other than "me too, please reopen" comments.
> > > >
> > > > --
> > > > Best Regards,
> > > > Vilius
> > > >
> > > > -----Original Message-----
> > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > Subject: GitHub Issues & Discussions enabled
> > > >
> > > > Hi folks,
> > > >
> > > > We are pleased to announce that GitHub Issues & Discussions.
> > > >
> > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > Jira is now read-only and we should now all use GitHub Issues.
> > > >
> > > > We have the following labels available:
> > > > - bug: for bug reports
> > > > - dependencies: for dependencies updates
> > > > - enhancement: for improvements on existing code
> > > > - feature: for a complete new features
> > > > - proposal: for a design proposal, big features
> > > > - stale: when the issue is "inactive" for more than 60 days
> > > >
> > > > Please use these labels to classify the issues.
> > > >
> > > > When you create a PR, you can associate it with an issue either in
> the
> > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > I also suggest using conventional commit messages in PR with the
> format
> > > > <type>(<scope>): <subject> where scope is optional. The type can be:
> > > > - feat: (a new feature is introduced with the changes)
> > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > - docs: (changes to the documentation)
> > > > - style: (formatting, missing semicolons, etc; no production code
> > change)
> > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > - test: (adding missing tests, refactoring tests; no production code
> > > > change)
> > > > - chore: (changes that do not relate to a fix or feature and don't
> > modify
> > > > src or test files (for example updating dependencies or change in
> > > > production code))
> > > > - perf – (performance improvements)
> > > > - ci – (continuous integration related)
> > > > - build – (changes that affect the build system or external
> > dependencies)
> > > > - revert – (reverts a previous commit)
> > > > That's a nice practice because GitHub can use that to create nice
> > Release
> > > > Notes.
> > > > Thanks to that, it's not necessary to create GH issues for all
> changes.
> > > >
> > > > For versions, we are using GitHub Projects (
> > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > You can assign several projects/versions per issue, and track the
> > status
> > > > of the versions.
> > > >
> > > > 2. GitHub Discussions
> > > > We also enabled GitHub Discussions where we can have technical
> > > discussions.
> > > > The GH Discussions are automatically going to the dev@ mailing list.
> > > >
> > > > Let us know if you have any questions.
> > > >
> > > > Regards
> > > > JB
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
Any update on this? Or any action needed from my end?
Best,
KP
On Wed, Apr 22, 2026 at 7:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> Sure, let me create the PRs for your review.
>
> Regards
> JB
>
> On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
>
> > Hi JB,
> >
> > Could you walk me through the process of enabling github issues for:
> >
> > - https://github.com/apache/activemq-nms-api
> > - https://github.com/apache/activemq-nms-amqp
> > - https://github.com/apache/activemq-nms-openwire
> >
> > Thanks,
> > KP
> >
> > On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi
> > >
> > > 1. About stale: the stale issues are flagged by not closed (only the PR
> > > could be closed by the stale bot). So the issues are still open (just
> > > flagged).
> > > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> > tickets
> > > to GH Issues. I'm creating issues manually for now (new issues). I will
> > run
> > > the migration soon. Again, Jira is still there, just read-only.
> > >
> > > Regards
> > > JB
> > >
> > > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > > dev@activemq.apache.org> wrote:
> > >
> > > > Nice!
> > > >
> > > > Will all old Jira issues be migrated to GitHub too?
> > > >
> > > > Also, I'm wondering, how "stale" issues will be managed? I would hate
> > to
> > > > see those bots automatically closing issues if they are "inactive". I
> > > > understand that sometimes there is a need to manage a backlog, but
> this
> > > > doesn't allow "voting" on issues with likes or other means of
> activity
> > > > other than "me too, please reopen" comments.
> > > >
> > > > --
> > > > Best Regards,
> > > > Vilius
> > > >
> > > > -----Original Message-----
> > > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > > Sent: Thursday, February 19, 2026 6:42 PM
> > > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > > Subject: GitHub Issues & Discussions enabled
> > > >
> > > > Hi folks,
> > > >
> > > > We are pleased to announce that GitHub Issues & Discussions.
> > > >
> > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > Jira is now read-only and we should now all use GitHub Issues.
> > > >
> > > > We have the following labels available:
> > > > - bug: for bug reports
> > > > - dependencies: for dependencies updates
> > > > - enhancement: for improvements on existing code
> > > > - feature: for a complete new features
> > > > - proposal: for a design proposal, big features
> > > > - stale: when the issue is "inactive" for more than 60 days
> > > >
> > > > Please use these labels to classify the issues.
> > > >
> > > > When you create a PR, you can associate it with an issue either in
> the
> > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > I also suggest using conventional commit messages in PR with the
> format
> > > > <type>(<scope>): <subject> where scope is optional. The type can be:
> > > > - feat: (a new feature is introduced with the changes)
> > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > - docs: (changes to the documentation)
> > > > - style: (formatting, missing semicolons, etc; no production code
> > change)
> > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > - test: (adding missing tests, refactoring tests; no production code
> > > > change)
> > > > - chore: (changes that do not relate to a fix or feature and don't
> > modify
> > > > src or test files (for example updating dependencies or change in
> > > > production code))
> > > > - perf – (performance improvements)
> > > > - ci – (continuous integration related)
> > > > - build – (changes that affect the build system or external
> > dependencies)
> > > > - revert – (reverts a previous commit)
> > > > That's a nice practice because GitHub can use that to create nice
> > Release
> > > > Notes.
> > > > Thanks to that, it's not necessary to create GH issues for all
> changes.
> > > >
> > > > For versions, we are using GitHub Projects (
> > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > You can assign several projects/versions per issue, and track the
> > status
> > > > of the versions.
> > > >
> > > > 2. GitHub Discussions
> > > > We also enabled GitHub Discussions where we can have technical
> > > discussions.
> > > > The GH Discussions are automatically going to the dev@ mailing list.
> > > >
> > > > Let us know if you have any questions.
> > > >
> > > > Regards
> > > > JB
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
Sure, let me create the PRs for your review.
Regards
JB
On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> Hi JB,
>
> Could you walk me through the process of enabling github issues for:
>
> - https://github.com/apache/activemq-nms-api
> - https://github.com/apache/activemq-nms-amqp
> - https://github.com/apache/activemq-nms-openwire
>
> Thanks,
> KP
>
> On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > 1. About stale: the stale issues are flagged by not closed (only the PR
> > could be closed by the stale bot). So the issues are still open (just
> > flagged).
> > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> tickets
> > to GH Issues. I'm creating issues manually for now (new issues). I will
> run
> > the migration soon. Again, Jira is still there, just read-only.
> >
> > Regards
> > JB
> >
> > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > dev@activemq.apache.org> wrote:
> >
> > > Nice!
> > >
> > > Will all old Jira issues be migrated to GitHub too?
> > >
> > > Also, I'm wondering, how "stale" issues will be managed? I would hate
> to
> > > see those bots automatically closing issues if they are "inactive". I
> > > understand that sometimes there is a need to manage a backlog, but this
> > > doesn't allow "voting" on issues with likes or other means of activity
> > > other than "me too, please reopen" comments.
> > >
> > > --
> > > Best Regards,
> > > Vilius
> > >
> > > -----Original Message-----
> > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > Sent: Thursday, February 19, 2026 6:42 PM
> > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > Subject: GitHub Issues & Discussions enabled
> > >
> > > Hi folks,
> > >
> > > We are pleased to announce that GitHub Issues & Discussions.
> > >
> > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > Jira is now read-only and we should now all use GitHub Issues.
> > >
> > > We have the following labels available:
> > > - bug: for bug reports
> > > - dependencies: for dependencies updates
> > > - enhancement: for improvements on existing code
> > > - feature: for a complete new features
> > > - proposal: for a design proposal, big features
> > > - stale: when the issue is "inactive" for more than 60 days
> > >
> > > Please use these labels to classify the issues.
> > >
> > > When you create a PR, you can associate it with an issue either in the
> > > GitHub UI or using "This closes #xxxx" in the comments.
> > > I also suggest using conventional commit messages in PR with the format
> > > <type>(<scope>): <subject> where scope is optional. The type can be:
> > > - feat: (a new feature is introduced with the changes)
> > > - fix: (bug fix has occurred, not a fix to a build script)
> > > - docs: (changes to the documentation)
> > > - style: (formatting, missing semicolons, etc; no production code
> change)
> > > - refactor: (refactoring production code, eg. renaming a variable)
> > > - test: (adding missing tests, refactoring tests; no production code
> > > change)
> > > - chore: (changes that do not relate to a fix or feature and don't
> modify
> > > src or test files (for example updating dependencies or change in
> > > production code))
> > > - perf – (performance improvements)
> > > - ci – (continuous integration related)
> > > - build – (changes that affect the build system or external
> dependencies)
> > > - revert – (reverts a previous commit)
> > > That's a nice practice because GitHub can use that to create nice
> Release
> > > Notes.
> > > Thanks to that, it's not necessary to create GH issues for all changes.
> > >
> > > For versions, we are using GitHub Projects (
> > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > You can assign several projects/versions per issue, and track the
> status
> > > of the versions.
> > >
> > > 2. GitHub Discussions
> > > We also enabled GitHub Discussions where we can have technical
> > discussions.
> > > The GH Discussions are automatically going to the dev@ mailing list.
> > >
> > > Let us know if you have any questions.
> > >
> > > Regards
> > > JB
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
Sure, let me create the PRs for your review.
Regards
JB
On Wed, Apr 22, 2026 at 12:21 AM Havret <ha...@apache.org> wrote:
> Hi JB,
>
> Could you walk me through the process of enabling github issues for:
>
> - https://github.com/apache/activemq-nms-api
> - https://github.com/apache/activemq-nms-amqp
> - https://github.com/apache/activemq-nms-openwire
>
> Thanks,
> KP
>
> On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > Hi
> >
> > 1. About stale: the stale issues are flagged by not closed (only the PR
> > could be closed by the stale bot). So the issues are still open (just
> > flagged).
> > 2. Yes, we have a script provided by the ASF infra to migrate Jira
> tickets
> > to GH Issues. I'm creating issues manually for now (new issues). I will
> run
> > the migration soon. Again, Jira is still there, just read-only.
> >
> > Regards
> > JB
> >
> > On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> > dev@activemq.apache.org> wrote:
> >
> > > Nice!
> > >
> > > Will all old Jira issues be migrated to GitHub too?
> > >
> > > Also, I'm wondering, how "stale" issues will be managed? I would hate
> to
> > > see those bots automatically closing issues if they are "inactive". I
> > > understand that sometimes there is a need to manage a backlog, but this
> > > doesn't allow "voting" on issues with likes or other means of activity
> > > other than "me too, please reopen" comments.
> > >
> > > --
> > > Best Regards,
> > > Vilius
> > >
> > > -----Original Message-----
> > > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > Sent: Thursday, February 19, 2026 6:42 PM
> > > To: dev@activemq.apache.org; users@activemq.apache.org
> > > Subject: GitHub Issues & Discussions enabled
> > >
> > > Hi folks,
> > >
> > > We are pleased to announce that GitHub Issues & Discussions.
> > >
> > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > Jira is now read-only and we should now all use GitHub Issues.
> > >
> > > We have the following labels available:
> > > - bug: for bug reports
> > > - dependencies: for dependencies updates
> > > - enhancement: for improvements on existing code
> > > - feature: for a complete new features
> > > - proposal: for a design proposal, big features
> > > - stale: when the issue is "inactive" for more than 60 days
> > >
> > > Please use these labels to classify the issues.
> > >
> > > When you create a PR, you can associate it with an issue either in the
> > > GitHub UI or using "This closes #xxxx" in the comments.
> > > I also suggest using conventional commit messages in PR with the format
> > > <type>(<scope>): <subject> where scope is optional. The type can be:
> > > - feat: (a new feature is introduced with the changes)
> > > - fix: (bug fix has occurred, not a fix to a build script)
> > > - docs: (changes to the documentation)
> > > - style: (formatting, missing semicolons, etc; no production code
> change)
> > > - refactor: (refactoring production code, eg. renaming a variable)
> > > - test: (adding missing tests, refactoring tests; no production code
> > > change)
> > > - chore: (changes that do not relate to a fix or feature and don't
> modify
> > > src or test files (for example updating dependencies or change in
> > > production code))
> > > - perf – (performance improvements)
> > > - ci – (continuous integration related)
> > > - build – (changes that affect the build system or external
> dependencies)
> > > - revert – (reverts a previous commit)
> > > That's a nice practice because GitHub can use that to create nice
> Release
> > > Notes.
> > > Thanks to that, it's not necessary to create GH issues for all changes.
> > >
> > > For versions, we are using GitHub Projects (
> > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > You can assign several projects/versions per issue, and track the
> status
> > > of the versions.
> > >
> > > 2. GitHub Discussions
> > > We also enabled GitHub Discussions where we can have technical
> > discussions.
> > > The GH Discussions are automatically going to the dev@ mailing list.
> > >
> > > Let us know if you have any questions.
> > >
> > > Regards
> > > JB
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
Could you walk me through the process of enabling github issues for:
- https://github.com/apache/activemq-nms-api
- https://github.com/apache/activemq-nms-amqp
- https://github.com/apache/activemq-nms-openwire
Thanks,
KP
On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> 1. About stale: the stale issues are flagged by not closed (only the PR
> could be closed by the stale bot). So the issues are still open (just
> flagged).
> 2. Yes, we have a script provided by the ASF infra to migrate Jira tickets
> to GH Issues. I'm creating issues manually for now (new issues). I will run
> the migration soon. Again, Jira is still there, just read-only.
>
> Regards
> JB
>
> On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> dev@activemq.apache.org> wrote:
>
> > Nice!
> >
> > Will all old Jira issues be migrated to GitHub too?
> >
> > Also, I'm wondering, how "stale" issues will be managed? I would hate to
> > see those bots automatically closing issues if they are "inactive". I
> > understand that sometimes there is a need to manage a backlog, but this
> > doesn't allow "voting" on issues with likes or other means of activity
> > other than "me too, please reopen" comments.
> >
> > --
> > Best Regards,
> > Vilius
> >
> > -----Original Message-----
> > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > Sent: Thursday, February 19, 2026 6:42 PM
> > To: dev@activemq.apache.org; users@activemq.apache.org
> > Subject: GitHub Issues & Discussions enabled
> >
> > Hi folks,
> >
> > We are pleased to announce that GitHub Issues & Discussions.
> >
> > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > Jira is now read-only and we should now all use GitHub Issues.
> >
> > We have the following labels available:
> > - bug: for bug reports
> > - dependencies: for dependencies updates
> > - enhancement: for improvements on existing code
> > - feature: for a complete new features
> > - proposal: for a design proposal, big features
> > - stale: when the issue is "inactive" for more than 60 days
> >
> > Please use these labels to classify the issues.
> >
> > When you create a PR, you can associate it with an issue either in the
> > GitHub UI or using "This closes #xxxx" in the comments.
> > I also suggest using conventional commit messages in PR with the format
> > <type>(<scope>): <subject> where scope is optional. The type can be:
> > - feat: (a new feature is introduced with the changes)
> > - fix: (bug fix has occurred, not a fix to a build script)
> > - docs: (changes to the documentation)
> > - style: (formatting, missing semicolons, etc; no production code change)
> > - refactor: (refactoring production code, eg. renaming a variable)
> > - test: (adding missing tests, refactoring tests; no production code
> > change)
> > - chore: (changes that do not relate to a fix or feature and don't modify
> > src or test files (for example updating dependencies or change in
> > production code))
> > - perf – (performance improvements)
> > - ci – (continuous integration related)
> > - build – (changes that affect the build system or external dependencies)
> > - revert – (reverts a previous commit)
> > That's a nice practice because GitHub can use that to create nice Release
> > Notes.
> > Thanks to that, it's not necessary to create GH issues for all changes.
> >
> > For versions, we are using GitHub Projects (
> > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > You can assign several projects/versions per issue, and track the status
> > of the versions.
> >
> > 2. GitHub Discussions
> > We also enabled GitHub Discussions where we can have technical
> discussions.
> > The GH Discussions are automatically going to the dev@ mailing list.
> >
> > Let us know if you have any questions.
> >
> > Regards
> > JB
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
Could you walk me through the process of enabling github issues for:
- https://github.com/apache/activemq-nms-api
- https://github.com/apache/activemq-nms-amqp
- https://github.com/apache/activemq-nms-openwire
Thanks,
KP
On Fri, Feb 20, 2026 at 8:37 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi
>
> 1. About stale: the stale issues are flagged by not closed (only the PR
> could be closed by the stale bot). So the issues are still open (just
> flagged).
> 2. Yes, we have a script provided by the ASF infra to migrate Jira tickets
> to GH Issues. I'm creating issues manually for now (new issues). I will run
> the migration soon. Again, Jira is still there, just read-only.
>
> Regards
> JB
>
> On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
> dev@activemq.apache.org> wrote:
>
> > Nice!
> >
> > Will all old Jira issues be migrated to GitHub too?
> >
> > Also, I'm wondering, how "stale" issues will be managed? I would hate to
> > see those bots automatically closing issues if they are "inactive". I
> > understand that sometimes there is a need to manage a backlog, but this
> > doesn't allow "voting" on issues with likes or other means of activity
> > other than "me too, please reopen" comments.
> >
> > --
> > Best Regards,
> > Vilius
> >
> > -----Original Message-----
> > From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> > Sent: Thursday, February 19, 2026 6:42 PM
> > To: dev@activemq.apache.org; users@activemq.apache.org
> > Subject: GitHub Issues & Discussions enabled
> >
> > Hi folks,
> >
> > We are pleased to announce that GitHub Issues & Discussions.
> >
> > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > Jira is now read-only and we should now all use GitHub Issues.
> >
> > We have the following labels available:
> > - bug: for bug reports
> > - dependencies: for dependencies updates
> > - enhancement: for improvements on existing code
> > - feature: for a complete new features
> > - proposal: for a design proposal, big features
> > - stale: when the issue is "inactive" for more than 60 days
> >
> > Please use these labels to classify the issues.
> >
> > When you create a PR, you can associate it with an issue either in the
> > GitHub UI or using "This closes #xxxx" in the comments.
> > I also suggest using conventional commit messages in PR with the format
> > <type>(<scope>): <subject> where scope is optional. The type can be:
> > - feat: (a new feature is introduced with the changes)
> > - fix: (bug fix has occurred, not a fix to a build script)
> > - docs: (changes to the documentation)
> > - style: (formatting, missing semicolons, etc; no production code change)
> > - refactor: (refactoring production code, eg. renaming a variable)
> > - test: (adding missing tests, refactoring tests; no production code
> > change)
> > - chore: (changes that do not relate to a fix or feature and don't modify
> > src or test files (for example updating dependencies or change in
> > production code))
> > - perf – (performance improvements)
> > - ci – (continuous integration related)
> > - build – (changes that affect the build system or external dependencies)
> > - revert – (reverts a previous commit)
> > That's a nice practice because GitHub can use that to create nice Release
> > Notes.
> > Thanks to that, it's not necessary to create GH issues for all changes.
> >
> > For versions, we are using GitHub Projects (
> > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > You can assign several projects/versions per issue, and track the status
> > of the versions.
> >
> > 2. GitHub Discussions
> > We also enabled GitHub Discussions where we can have technical
> discussions.
> > The GH Discussions are automatically going to the dev@ mailing list.
> >
> > Let us know if you have any questions.
> >
> > Regards
> > JB
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
1. About stale: the stale issues are flagged by not closed (only the PR
could be closed by the stale bot). So the issues are still open (just
flagged).
2. Yes, we have a script provided by the ASF infra to migrate Jira tickets
to GH Issues. I'm creating issues manually for now (new issues). I will run
the migration soon. Again, Jira is still there, just read-only.
Regards
JB
On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
dev@activemq.apache.org> wrote:
> Nice!
>
> Will all old Jira issues be migrated to GitHub too?
>
> Also, I'm wondering, how "stale" issues will be managed? I would hate to
> see those bots automatically closing issues if they are "inactive". I
> understand that sometimes there is a need to manage a backlog, but this
> doesn't allow "voting" on issues with likes or other means of activity
> other than "me too, please reopen" comments.
>
> --
> Best Regards,
> Vilius
>
> -----Original Message-----
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Thursday, February 19, 2026 6:42 PM
> To: dev@activemq.apache.org; users@activemq.apache.org
> Subject: GitHub Issues & Discussions enabled
>
> Hi folks,
>
> We are pleased to announce that GitHub Issues & Discussions.
>
> 1. GitHub Issues (https://github.com/apache/activemq/issues)
> Jira is now read-only and we should now all use GitHub Issues.
>
> We have the following labels available:
> - bug: for bug reports
> - dependencies: for dependencies updates
> - enhancement: for improvements on existing code
> - feature: for a complete new features
> - proposal: for a design proposal, big features
> - stale: when the issue is "inactive" for more than 60 days
>
> Please use these labels to classify the issues.
>
> When you create a PR, you can associate it with an issue either in the
> GitHub UI or using "This closes #xxxx" in the comments.
> I also suggest using conventional commit messages in PR with the format
> <type>(<scope>): <subject> where scope is optional. The type can be:
> - feat: (a new feature is introduced with the changes)
> - fix: (bug fix has occurred, not a fix to a build script)
> - docs: (changes to the documentation)
> - style: (formatting, missing semicolons, etc; no production code change)
> - refactor: (refactoring production code, eg. renaming a variable)
> - test: (adding missing tests, refactoring tests; no production code
> change)
> - chore: (changes that do not relate to a fix or feature and don't modify
> src or test files (for example updating dependencies or change in
> production code))
> - perf – (performance improvements)
> - ci – (continuous integration related)
> - build – (changes that affect the build system or external dependencies)
> - revert – (reverts a previous commit)
> That's a nice practice because GitHub can use that to create nice Release
> Notes.
> Thanks to that, it's not necessary to create GH issues for all changes.
>
> For versions, we are using GitHub Projects (
> https://github.com/apache/activemq/projects?query=is%3Aopen).
> You can assign several projects/versions per issue, and track the status
> of the versions.
>
> 2. GitHub Discussions
> We also enabled GitHub Discussions where we can have technical discussions.
> The GH Discussions are automatically going to the dev@ mailing list.
>
> Let us know if you have any questions.
>
> Regards
> JB
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
1. About stale: the stale issues are flagged by not closed (only the PR
could be closed by the stale bot). So the issues are still open (just
flagged).
2. Yes, we have a script provided by the ASF infra to migrate Jira tickets
to GH Issues. I'm creating issues manually for now (new issues). I will run
the migration soon. Again, Jira is still there, just read-only.
Regards
JB
On Thu, Feb 19, 2026 at 10:27 PM Vilius Šumskas via dev <
dev@activemq.apache.org> wrote:
> Nice!
>
> Will all old Jira issues be migrated to GitHub too?
>
> Also, I'm wondering, how "stale" issues will be managed? I would hate to
> see those bots automatically closing issues if they are "inactive". I
> understand that sometimes there is a need to manage a backlog, but this
> doesn't allow "voting" on issues with likes or other means of activity
> other than "me too, please reopen" comments.
>
> --
> Best Regards,
> Vilius
>
> -----Original Message-----
> From: Jean-Baptiste Onofré <jb...@nanthrax.net>
> Sent: Thursday, February 19, 2026 6:42 PM
> To: dev@activemq.apache.org; users@activemq.apache.org
> Subject: GitHub Issues & Discussions enabled
>
> Hi folks,
>
> We are pleased to announce that GitHub Issues & Discussions.
>
> 1. GitHub Issues (https://github.com/apache/activemq/issues)
> Jira is now read-only and we should now all use GitHub Issues.
>
> We have the following labels available:
> - bug: for bug reports
> - dependencies: for dependencies updates
> - enhancement: for improvements on existing code
> - feature: for a complete new features
> - proposal: for a design proposal, big features
> - stale: when the issue is "inactive" for more than 60 days
>
> Please use these labels to classify the issues.
>
> When you create a PR, you can associate it with an issue either in the
> GitHub UI or using "This closes #xxxx" in the comments.
> I also suggest using conventional commit messages in PR with the format
> <type>(<scope>): <subject> where scope is optional. The type can be:
> - feat: (a new feature is introduced with the changes)
> - fix: (bug fix has occurred, not a fix to a build script)
> - docs: (changes to the documentation)
> - style: (formatting, missing semicolons, etc; no production code change)
> - refactor: (refactoring production code, eg. renaming a variable)
> - test: (adding missing tests, refactoring tests; no production code
> change)
> - chore: (changes that do not relate to a fix or feature and don't modify
> src or test files (for example updating dependencies or change in
> production code))
> - perf – (performance improvements)
> - ci – (continuous integration related)
> - build – (changes that affect the build system or external dependencies)
> - revert – (reverts a previous commit)
> That's a nice practice because GitHub can use that to create nice Release
> Notes.
> Thanks to that, it's not necessary to create GH issues for all changes.
>
> For versions, we are using GitHub Projects (
> https://github.com/apache/activemq/projects?query=is%3Aopen).
> You can assign several projects/versions per issue, and track the status
> of the versions.
>
> 2. GitHub Discussions
> We also enabled GitHub Discussions where we can have technical discussions.
> The GH Discussions are automatically going to the dev@ mailing list.
>
> Let us know if you have any questions.
>
> Regards
> JB
>
RE: GitHub Issues & Discussions enabled
Posted by Vilius Šumskas via users <us...@activemq.apache.org>.
Nice!
Will all old Jira issues be migrated to GitHub too?
Also, I'm wondering, how "stale" issues will be managed? I would hate to see those bots automatically closing issues if they are "inactive". I understand that sometimes there is a need to manage a backlog, but this doesn't allow "voting" on issues with likes or other means of activity other than "me too, please reopen" comments.
--
Best Regards,
Vilius
-----Original Message-----
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Thursday, February 19, 2026 6:42 PM
To: dev@activemq.apache.org; users@activemq.apache.org
Subject: GitHub Issues & Discussions enabled
Hi folks,
We are pleased to announce that GitHub Issues & Discussions.
1. GitHub Issues (https://github.com/apache/activemq/issues)
Jira is now read-only and we should now all use GitHub Issues.
We have the following labels available:
- bug: for bug reports
- dependencies: for dependencies updates
- enhancement: for improvements on existing code
- feature: for a complete new features
- proposal: for a design proposal, big features
- stale: when the issue is "inactive" for more than 60 days
Please use these labels to classify the issues.
When you create a PR, you can associate it with an issue either in the GitHub UI or using "This closes #xxxx" in the comments.
I also suggest using conventional commit messages in PR with the format <type>(<scope>): <subject> where scope is optional. The type can be:
- feat: (a new feature is introduced with the changes)
- fix: (bug fix has occurred, not a fix to a build script)
- docs: (changes to the documentation)
- style: (formatting, missing semicolons, etc; no production code change)
- refactor: (refactoring production code, eg. renaming a variable)
- test: (adding missing tests, refactoring tests; no production code change)
- chore: (changes that do not relate to a fix or feature and don't modify src or test files (for example updating dependencies or change in production code))
- perf – (performance improvements)
- ci – (continuous integration related)
- build – (changes that affect the build system or external dependencies)
- revert – (reverts a previous commit)
That's a nice practice because GitHub can use that to create nice Release Notes.
Thanks to that, it's not necessary to create GH issues for all changes.
For versions, we are using GitHub Projects ( https://github.com/apache/activemq/projects?query=is%3Aopen).
You can assign several projects/versions per issue, and track the status of the versions.
2. GitHub Discussions
We also enabled GitHub Discussions where we can have technical discussions.
The GH Discussions are automatically going to the dev@ mailing list.
Let us know if you have any questions.
Regards
JB
Re: GitHub Issues & Discussions enabled
Posted by Matt Pavlovich <ma...@apache.org>.
GH please =)
> On Feb 19, 2026, at 12:14 PM, Havret <ha...@apache.org> wrote:
>
> Hi JB,
>
> What about the satellite projects like nms, nms-amqp and nms-openwire?
>
> What should we use there?
>
> Best,
> KP
>
> On Thu, Feb 19, 2026 at 6:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> By the way, just to clarify about the conventional commit message, it's a
>> suggestion, you are free to use it or not :)
>>
>> Personally, I will force myself to do use it (to force myself to think
>> about the kind of changes I'm doing).
>>
>> Regards
>> JB
>>
>> On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>>
>>> That looks great JB. Thanks for pushing on it.
>>> I'm sure we'll learn and adjust as we go along.
>>>
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
>>> wrote:
>>>
>>>> Thanks for all your efforts on this! It would be good to add a md file
>>>> with all this info and link it from the webpage and main README.md
>>>>
>>>> A couple of follow-ons:
>>>>
>>>> 1. I’m playing around with Milestones as a way to track long running
>>>> feature groups across version releases — ie JMS 3.0/2.1
>>>>
>>>> 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
>>>> this allows for better visibility across orgs and repos.
>>>>
>>>> 3. Projects allow us to link issues in dependencies in other orgs/repos
>>>> that fix things that we find or are related to a release for easier
>>>> discovery by end-users.
>>>>
>>>> More to come!
>>>>
>>>> Thanks,
>>>> Matt Pavlovich
>>>>
>>>>> On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> wrote:
>>>>>
>>>>> Hi folks,
>>>>>
>>>>> We are pleased to announce that GitHub Issues & Discussions.
>>>>>
>>>>> 1. GitHub Issues (https://github.com/apache/activemq/issues)
>>>>> Jira is now read-only and we should now all use GitHub Issues.
>>>>>
>>>>> We have the following labels available:
>>>>> - bug: for bug reports
>>>>> - dependencies: for dependencies updates
>>>>> - enhancement: for improvements on existing code
>>>>> - feature: for a complete new features
>>>>> - proposal: for a design proposal, big features
>>>>> - stale: when the issue is "inactive" for more than 60 days
>>>>>
>>>>> Please use these labels to classify the issues.
>>>>>
>>>>> When you create a PR, you can associate it with an issue either in
>> the
>>>>> GitHub UI or using "This closes #xxxx" in the comments.
>>>>> I also suggest using conventional commit messages in PR with the
>>>>> format <type>(<scope>): <subject> where scope is optional. The type
>> can
>>>> be:
>>>>> - feat: (a new feature is introduced with the changes)
>>>>> - fix: (bug fix has occurred, not a fix to a build script)
>>>>> - docs: (changes to the documentation)
>>>>> - style: (formatting, missing semicolons, etc; no production code
>>> change)
>>>>> - refactor: (refactoring production code, eg. renaming a variable)
>>>>> - test: (adding missing tests, refactoring tests; no production code
>>>> change)
>>>>> - chore: (changes that do not relate to a fix or feature and don't
>>> modify
>>>>> src or test files (for example updating dependencies or change in
>>>>> production code))
>>>>> - perf – (performance improvements)
>>>>> - ci – (continuous integration related)
>>>>> - build – (changes that affect the build system or external
>>> dependencies)
>>>>> - revert – (reverts a previous commit)
>>>>> That's a nice practice because GitHub can use that to create nice
>>> Release
>>>>> Notes.
>>>>> Thanks to that, it's not necessary to create GH issues for all
>> changes.
>>>>>
>>>>> For versions, we are using GitHub Projects (
>>>>> https://github.com/apache/activemq/projects?query=is%3Aopen).
>>>>> You can assign several projects/versions per issue, and track the
>>> status
>>>> of
>>>>> the versions.
>>>>>
>>>>> 2. GitHub Discussions
>>>>> We also enabled GitHub Discussions where we can have technical
>>>> discussions.
>>>>> The GH Discussions are automatically going to the dev@ mailing list.
>>>>>
>>>>> Let us know if you have any questions.
>>>>>
>>>>> Regards
>>>>> JB
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
>>>> For additional commands, e-mail: dev-help@activemq.apache.org
>>>> For further information, visit: https://activemq.apache.org/contact
>>>>
>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: GitHub Issues & Discussions enabled
Posted by Matt Pavlovich <ma...@apache.org>.
GH please =)
> On Feb 19, 2026, at 12:14 PM, Havret <ha...@apache.org> wrote:
>
> Hi JB,
>
> What about the satellite projects like nms, nms-amqp and nms-openwire?
>
> What should we use there?
>
> Best,
> KP
>
> On Thu, Feb 19, 2026 at 6:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> By the way, just to clarify about the conventional commit message, it's a
>> suggestion, you are free to use it or not :)
>>
>> Personally, I will force myself to do use it (to force myself to think
>> about the kind of changes I'm doing).
>>
>> Regards
>> JB
>>
>> On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
>> jlmonteiro@tomitribe.com> wrote:
>>
>>> That looks great JB. Thanks for pushing on it.
>>> I'm sure we'll learn and adjust as we go along.
>>>
>>>
>>> --
>>> Jean-Louis Monteiro
>>> http://twitter.com/jlouismonteiro
>>> http://www.tomitribe.com
>>>
>>>
>>> On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
>>> wrote:
>>>
>>>> Thanks for all your efforts on this! It would be good to add a md file
>>>> with all this info and link it from the webpage and main README.md
>>>>
>>>> A couple of follow-ons:
>>>>
>>>> 1. I’m playing around with Milestones as a way to track long running
>>>> feature groups across version releases — ie JMS 3.0/2.1
>>>>
>>>> 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
>>>> this allows for better visibility across orgs and repos.
>>>>
>>>> 3. Projects allow us to link issues in dependencies in other orgs/repos
>>>> that fix things that we find or are related to a release for easier
>>>> discovery by end-users.
>>>>
>>>> More to come!
>>>>
>>>> Thanks,
>>>> Matt Pavlovich
>>>>
>>>>> On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> wrote:
>>>>>
>>>>> Hi folks,
>>>>>
>>>>> We are pleased to announce that GitHub Issues & Discussions.
>>>>>
>>>>> 1. GitHub Issues (https://github.com/apache/activemq/issues)
>>>>> Jira is now read-only and we should now all use GitHub Issues.
>>>>>
>>>>> We have the following labels available:
>>>>> - bug: for bug reports
>>>>> - dependencies: for dependencies updates
>>>>> - enhancement: for improvements on existing code
>>>>> - feature: for a complete new features
>>>>> - proposal: for a design proposal, big features
>>>>> - stale: when the issue is "inactive" for more than 60 days
>>>>>
>>>>> Please use these labels to classify the issues.
>>>>>
>>>>> When you create a PR, you can associate it with an issue either in
>> the
>>>>> GitHub UI or using "This closes #xxxx" in the comments.
>>>>> I also suggest using conventional commit messages in PR with the
>>>>> format <type>(<scope>): <subject> where scope is optional. The type
>> can
>>>> be:
>>>>> - feat: (a new feature is introduced with the changes)
>>>>> - fix: (bug fix has occurred, not a fix to a build script)
>>>>> - docs: (changes to the documentation)
>>>>> - style: (formatting, missing semicolons, etc; no production code
>>> change)
>>>>> - refactor: (refactoring production code, eg. renaming a variable)
>>>>> - test: (adding missing tests, refactoring tests; no production code
>>>> change)
>>>>> - chore: (changes that do not relate to a fix or feature and don't
>>> modify
>>>>> src or test files (for example updating dependencies or change in
>>>>> production code))
>>>>> - perf – (performance improvements)
>>>>> - ci – (continuous integration related)
>>>>> - build – (changes that affect the build system or external
>>> dependencies)
>>>>> - revert – (reverts a previous commit)
>>>>> That's a nice practice because GitHub can use that to create nice
>>> Release
>>>>> Notes.
>>>>> Thanks to that, it's not necessary to create GH issues for all
>> changes.
>>>>>
>>>>> For versions, we are using GitHub Projects (
>>>>> https://github.com/apache/activemq/projects?query=is%3Aopen).
>>>>> You can assign several projects/versions per issue, and track the
>>> status
>>>> of
>>>>> the versions.
>>>>>
>>>>> 2. GitHub Discussions
>>>>> We also enabled GitHub Discussions where we can have technical
>>>> discussions.
>>>>> The GH Discussions are automatically going to the dev@ mailing list.
>>>>>
>>>>> Let us know if you have any questions.
>>>>>
>>>>> Regards
>>>>> JB
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
>>>> For additional commands, e-mail: dev-help@activemq.apache.org
>>>> For further information, visit: https://activemq.apache.org/contact
>>>>
>>>>
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
Just let me know. Your Jira is still active (not read only), so you have
the choice.
If you want to use GitHub Issues/Discussion, just let me know, we can
create dedicated labels.
Thoughts ?
Regards
JB
On Thu, Feb 19, 2026 at 7:14 PM Havret <ha...@apache.org> wrote:
> Hi JB,
>
> What about the satellite projects like nms, nms-amqp and nms-openwire?
>
> What should we use there?
>
> Best,
> KP
>
> On Thu, Feb 19, 2026 at 6:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > By the way, just to clarify about the conventional commit message, it's a
> > suggestion, you are free to use it or not :)
> >
> > Personally, I will force myself to do use it (to force myself to think
> > about the kind of changes I'm doing).
> >
> > Regards
> > JB
> >
> > On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> wrote:
> >
> > > That looks great JB. Thanks for pushing on it.
> > > I'm sure we'll learn and adjust as we go along.
> > >
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
> > > wrote:
> > >
> > > > Thanks for all your efforts on this! It would be good to add a md
> file
> > > > with all this info and link it from the webpage and main README.md
> > > >
> > > > A couple of follow-ons:
> > > >
> > > > 1. I’m playing around with Milestones as a way to track long running
> > > > feature groups across version releases — ie JMS 3.0/2.1
> > > >
> > > > 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’
> —
> > > > this allows for better visibility across orgs and repos.
> > > >
> > > > 3. Projects allow us to link issues in dependencies in other
> orgs/repos
> > > > that fix things that we find or are related to a release for easier
> > > > discovery by end-users.
> > > >
> > > > More to come!
> > > >
> > > > Thanks,
> > > > Matt Pavlovich
> > > >
> > > > > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <
> jb@nanthrax.net>
> > > > wrote:
> > > > >
> > > > > Hi folks,
> > > > >
> > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > >
> > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > >
> > > > > We have the following labels available:
> > > > > - bug: for bug reports
> > > > > - dependencies: for dependencies updates
> > > > > - enhancement: for improvements on existing code
> > > > > - feature: for a complete new features
> > > > > - proposal: for a design proposal, big features
> > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > >
> > > > > Please use these labels to classify the issues.
> > > > >
> > > > > When you create a PR, you can associate it with an issue either in
> > the
> > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > I also suggest using conventional commit messages in PR with the
> > > > > format <type>(<scope>): <subject> where scope is optional. The type
> > can
> > > > be:
> > > > > - feat: (a new feature is introduced with the changes)
> > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > - docs: (changes to the documentation)
> > > > > - style: (formatting, missing semicolons, etc; no production code
> > > change)
> > > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > > - test: (adding missing tests, refactoring tests; no production
> code
> > > > change)
> > > > > - chore: (changes that do not relate to a fix or feature and don't
> > > modify
> > > > > src or test files (for example updating dependencies or change in
> > > > > production code))
> > > > > - perf – (performance improvements)
> > > > > - ci – (continuous integration related)
> > > > > - build – (changes that affect the build system or external
> > > dependencies)
> > > > > - revert – (reverts a previous commit)
> > > > > That's a nice practice because GitHub can use that to create nice
> > > Release
> > > > > Notes.
> > > > > Thanks to that, it's not necessary to create GH issues for all
> > changes.
> > > > >
> > > > > For versions, we are using GitHub Projects (
> > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > You can assign several projects/versions per issue, and track the
> > > status
> > > > of
> > > > > the versions.
> > > > >
> > > > > 2. GitHub Discussions
> > > > > We also enabled GitHub Discussions where we can have technical
> > > > discussions.
> > > > > The GH Discussions are automatically going to the dev@ mailing
> list.
> > > > >
> > > > > Let us know if you have any questions.
> > > > >
> > > > > Regards
> > > > > JB
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> > > > For additional commands, e-mail: dev-help@activemq.apache.org
> > > > For further information, visit: https://activemq.apache.org/contact
> > > >
> > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi
Just let me know. Your Jira is still active (not read only), so you have
the choice.
If you want to use GitHub Issues/Discussion, just let me know, we can
create dedicated labels.
Thoughts ?
Regards
JB
On Thu, Feb 19, 2026 at 7:14 PM Havret <ha...@apache.org> wrote:
> Hi JB,
>
> What about the satellite projects like nms, nms-amqp and nms-openwire?
>
> What should we use there?
>
> Best,
> KP
>
> On Thu, Feb 19, 2026 at 6:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > By the way, just to clarify about the conventional commit message, it's a
> > suggestion, you are free to use it or not :)
> >
> > Personally, I will force myself to do use it (to force myself to think
> > about the kind of changes I'm doing).
> >
> > Regards
> > JB
> >
> > On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
> > jlmonteiro@tomitribe.com> wrote:
> >
> > > That looks great JB. Thanks for pushing on it.
> > > I'm sure we'll learn and adjust as we go along.
> > >
> > >
> > > --
> > > Jean-Louis Monteiro
> > > http://twitter.com/jlouismonteiro
> > > http://www.tomitribe.com
> > >
> > >
> > > On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
> > > wrote:
> > >
> > > > Thanks for all your efforts on this! It would be good to add a md
> file
> > > > with all this info and link it from the webpage and main README.md
> > > >
> > > > A couple of follow-ons:
> > > >
> > > > 1. I’m playing around with Milestones as a way to track long running
> > > > feature groups across version releases — ie JMS 3.0/2.1
> > > >
> > > > 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’
> —
> > > > this allows for better visibility across orgs and repos.
> > > >
> > > > 3. Projects allow us to link issues in dependencies in other
> orgs/repos
> > > > that fix things that we find or are related to a release for easier
> > > > discovery by end-users.
> > > >
> > > > More to come!
> > > >
> > > > Thanks,
> > > > Matt Pavlovich
> > > >
> > > > > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <
> jb@nanthrax.net>
> > > > wrote:
> > > > >
> > > > > Hi folks,
> > > > >
> > > > > We are pleased to announce that GitHub Issues & Discussions.
> > > > >
> > > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > > Jira is now read-only and we should now all use GitHub Issues.
> > > > >
> > > > > We have the following labels available:
> > > > > - bug: for bug reports
> > > > > - dependencies: for dependencies updates
> > > > > - enhancement: for improvements on existing code
> > > > > - feature: for a complete new features
> > > > > - proposal: for a design proposal, big features
> > > > > - stale: when the issue is "inactive" for more than 60 days
> > > > >
> > > > > Please use these labels to classify the issues.
> > > > >
> > > > > When you create a PR, you can associate it with an issue either in
> > the
> > > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > > I also suggest using conventional commit messages in PR with the
> > > > > format <type>(<scope>): <subject> where scope is optional. The type
> > can
> > > > be:
> > > > > - feat: (a new feature is introduced with the changes)
> > > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > > - docs: (changes to the documentation)
> > > > > - style: (formatting, missing semicolons, etc; no production code
> > > change)
> > > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > > - test: (adding missing tests, refactoring tests; no production
> code
> > > > change)
> > > > > - chore: (changes that do not relate to a fix or feature and don't
> > > modify
> > > > > src or test files (for example updating dependencies or change in
> > > > > production code))
> > > > > - perf – (performance improvements)
> > > > > - ci – (continuous integration related)
> > > > > - build – (changes that affect the build system or external
> > > dependencies)
> > > > > - revert – (reverts a previous commit)
> > > > > That's a nice practice because GitHub can use that to create nice
> > > Release
> > > > > Notes.
> > > > > Thanks to that, it's not necessary to create GH issues for all
> > changes.
> > > > >
> > > > > For versions, we are using GitHub Projects (
> > > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > > You can assign several projects/versions per issue, and track the
> > > status
> > > > of
> > > > > the versions.
> > > > >
> > > > > 2. GitHub Discussions
> > > > > We also enabled GitHub Discussions where we can have technical
> > > > discussions.
> > > > > The GH Discussions are automatically going to the dev@ mailing
> list.
> > > > >
> > > > > Let us know if you have any questions.
> > > > >
> > > > > Regards
> > > > > JB
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> > > > For additional commands, e-mail: dev-help@activemq.apache.org
> > > > For further information, visit: https://activemq.apache.org/contact
> > > >
> > > >
> > > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
What about the satellite projects like nms, nms-amqp and nms-openwire?
What should we use there?
Best,
KP
On Thu, Feb 19, 2026 at 6:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> By the way, just to clarify about the conventional commit message, it's a
> suggestion, you are free to use it or not :)
>
> Personally, I will force myself to do use it (to force myself to think
> about the kind of changes I'm doing).
>
> Regards
> JB
>
> On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > That looks great JB. Thanks for pushing on it.
> > I'm sure we'll learn and adjust as we go along.
> >
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
> > wrote:
> >
> > > Thanks for all your efforts on this! It would be good to add a md file
> > > with all this info and link it from the webpage and main README.md
> > >
> > > A couple of follow-ons:
> > >
> > > 1. I’m playing around with Milestones as a way to track long running
> > > feature groups across version releases — ie JMS 3.0/2.1
> > >
> > > 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
> > > this allows for better visibility across orgs and repos.
> > >
> > > 3. Projects allow us to link issues in dependencies in other orgs/repos
> > > that fix things that we find or are related to a release for easier
> > > discovery by end-users.
> > >
> > > More to come!
> > >
> > > Thanks,
> > > Matt Pavlovich
> > >
> > > > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > We are pleased to announce that GitHub Issues & Discussions.
> > > >
> > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > Jira is now read-only and we should now all use GitHub Issues.
> > > >
> > > > We have the following labels available:
> > > > - bug: for bug reports
> > > > - dependencies: for dependencies updates
> > > > - enhancement: for improvements on existing code
> > > > - feature: for a complete new features
> > > > - proposal: for a design proposal, big features
> > > > - stale: when the issue is "inactive" for more than 60 days
> > > >
> > > > Please use these labels to classify the issues.
> > > >
> > > > When you create a PR, you can associate it with an issue either in
> the
> > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > I also suggest using conventional commit messages in PR with the
> > > > format <type>(<scope>): <subject> where scope is optional. The type
> can
> > > be:
> > > > - feat: (a new feature is introduced with the changes)
> > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > - docs: (changes to the documentation)
> > > > - style: (formatting, missing semicolons, etc; no production code
> > change)
> > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > - test: (adding missing tests, refactoring tests; no production code
> > > change)
> > > > - chore: (changes that do not relate to a fix or feature and don't
> > modify
> > > > src or test files (for example updating dependencies or change in
> > > > production code))
> > > > - perf – (performance improvements)
> > > > - ci – (continuous integration related)
> > > > - build – (changes that affect the build system or external
> > dependencies)
> > > > - revert – (reverts a previous commit)
> > > > That's a nice practice because GitHub can use that to create nice
> > Release
> > > > Notes.
> > > > Thanks to that, it's not necessary to create GH issues for all
> changes.
> > > >
> > > > For versions, we are using GitHub Projects (
> > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > You can assign several projects/versions per issue, and track the
> > status
> > > of
> > > > the versions.
> > > >
> > > > 2. GitHub Discussions
> > > > We also enabled GitHub Discussions where we can have technical
> > > discussions.
> > > > The GH Discussions are automatically going to the dev@ mailing list.
> > > >
> > > > Let us know if you have any questions.
> > > >
> > > > Regards
> > > > JB
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> > > For additional commands, e-mail: dev-help@activemq.apache.org
> > > For further information, visit: https://activemq.apache.org/contact
> > >
> > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Havret <ha...@apache.org>.
Hi JB,
What about the satellite projects like nms, nms-amqp and nms-openwire?
What should we use there?
Best,
KP
On Thu, Feb 19, 2026 at 6:37 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> By the way, just to clarify about the conventional commit message, it's a
> suggestion, you are free to use it or not :)
>
> Personally, I will force myself to do use it (to force myself to think
> about the kind of changes I'm doing).
>
> Regards
> JB
>
> On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
> jlmonteiro@tomitribe.com> wrote:
>
> > That looks great JB. Thanks for pushing on it.
> > I'm sure we'll learn and adjust as we go along.
> >
> >
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
> > wrote:
> >
> > > Thanks for all your efforts on this! It would be good to add a md file
> > > with all this info and link it from the webpage and main README.md
> > >
> > > A couple of follow-ons:
> > >
> > > 1. I’m playing around with Milestones as a way to track long running
> > > feature groups across version releases — ie JMS 3.0/2.1
> > >
> > > 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
> > > this allows for better visibility across orgs and repos.
> > >
> > > 3. Projects allow us to link issues in dependencies in other orgs/repos
> > > that fix things that we find or are related to a release for easier
> > > discovery by end-users.
> > >
> > > More to come!
> > >
> > > Thanks,
> > > Matt Pavlovich
> > >
> > > > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> > > wrote:
> > > >
> > > > Hi folks,
> > > >
> > > > We are pleased to announce that GitHub Issues & Discussions.
> > > >
> > > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > > Jira is now read-only and we should now all use GitHub Issues.
> > > >
> > > > We have the following labels available:
> > > > - bug: for bug reports
> > > > - dependencies: for dependencies updates
> > > > - enhancement: for improvements on existing code
> > > > - feature: for a complete new features
> > > > - proposal: for a design proposal, big features
> > > > - stale: when the issue is "inactive" for more than 60 days
> > > >
> > > > Please use these labels to classify the issues.
> > > >
> > > > When you create a PR, you can associate it with an issue either in
> the
> > > > GitHub UI or using "This closes #xxxx" in the comments.
> > > > I also suggest using conventional commit messages in PR with the
> > > > format <type>(<scope>): <subject> where scope is optional. The type
> can
> > > be:
> > > > - feat: (a new feature is introduced with the changes)
> > > > - fix: (bug fix has occurred, not a fix to a build script)
> > > > - docs: (changes to the documentation)
> > > > - style: (formatting, missing semicolons, etc; no production code
> > change)
> > > > - refactor: (refactoring production code, eg. renaming a variable)
> > > > - test: (adding missing tests, refactoring tests; no production code
> > > change)
> > > > - chore: (changes that do not relate to a fix or feature and don't
> > modify
> > > > src or test files (for example updating dependencies or change in
> > > > production code))
> > > > - perf – (performance improvements)
> > > > - ci – (continuous integration related)
> > > > - build – (changes that affect the build system or external
> > dependencies)
> > > > - revert – (reverts a previous commit)
> > > > That's a nice practice because GitHub can use that to create nice
> > Release
> > > > Notes.
> > > > Thanks to that, it's not necessary to create GH issues for all
> changes.
> > > >
> > > > For versions, we are using GitHub Projects (
> > > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > > You can assign several projects/versions per issue, and track the
> > status
> > > of
> > > > the versions.
> > > >
> > > > 2. GitHub Discussions
> > > > We also enabled GitHub Discussions where we can have technical
> > > discussions.
> > > > The GH Discussions are automatically going to the dev@ mailing list.
> > > >
> > > > Let us know if you have any questions.
> > > >
> > > > Regards
> > > > JB
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> > > For additional commands, e-mail: dev-help@activemq.apache.org
> > > For further information, visit: https://activemq.apache.org/contact
> > >
> > >
> > >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
By the way, just to clarify about the conventional commit message, it's a
suggestion, you are free to use it or not :)
Personally, I will force myself to do use it (to force myself to think
about the kind of changes I'm doing).
Regards
JB
On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> That looks great JB. Thanks for pushing on it.
> I'm sure we'll learn and adjust as we go along.
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
> wrote:
>
> > Thanks for all your efforts on this! It would be good to add a md file
> > with all this info and link it from the webpage and main README.md
> >
> > A couple of follow-ons:
> >
> > 1. I’m playing around with Milestones as a way to track long running
> > feature groups across version releases — ie JMS 3.0/2.1
> >
> > 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
> > this allows for better visibility across orgs and repos.
> >
> > 3. Projects allow us to link issues in dependencies in other orgs/repos
> > that fix things that we find or are related to a release for easier
> > discovery by end-users.
> >
> > More to come!
> >
> > Thanks,
> > Matt Pavlovich
> >
> > > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> > >
> > > Hi folks,
> > >
> > > We are pleased to announce that GitHub Issues & Discussions.
> > >
> > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > Jira is now read-only and we should now all use GitHub Issues.
> > >
> > > We have the following labels available:
> > > - bug: for bug reports
> > > - dependencies: for dependencies updates
> > > - enhancement: for improvements on existing code
> > > - feature: for a complete new features
> > > - proposal: for a design proposal, big features
> > > - stale: when the issue is "inactive" for more than 60 days
> > >
> > > Please use these labels to classify the issues.
> > >
> > > When you create a PR, you can associate it with an issue either in the
> > > GitHub UI or using "This closes #xxxx" in the comments.
> > > I also suggest using conventional commit messages in PR with the
> > > format <type>(<scope>): <subject> where scope is optional. The type can
> > be:
> > > - feat: (a new feature is introduced with the changes)
> > > - fix: (bug fix has occurred, not a fix to a build script)
> > > - docs: (changes to the documentation)
> > > - style: (formatting, missing semicolons, etc; no production code
> change)
> > > - refactor: (refactoring production code, eg. renaming a variable)
> > > - test: (adding missing tests, refactoring tests; no production code
> > change)
> > > - chore: (changes that do not relate to a fix or feature and don't
> modify
> > > src or test files (for example updating dependencies or change in
> > > production code))
> > > - perf – (performance improvements)
> > > - ci – (continuous integration related)
> > > - build – (changes that affect the build system or external
> dependencies)
> > > - revert – (reverts a previous commit)
> > > That's a nice practice because GitHub can use that to create nice
> Release
> > > Notes.
> > > Thanks to that, it's not necessary to create GH issues for all changes.
> > >
> > > For versions, we are using GitHub Projects (
> > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > You can assign several projects/versions per issue, and track the
> status
> > of
> > > the versions.
> > >
> > > 2. GitHub Discussions
> > > We also enabled GitHub Discussions where we can have technical
> > discussions.
> > > The GH Discussions are automatically going to the dev@ mailing list.
> > >
> > > Let us know if you have any questions.
> > >
> > > Regards
> > > JB
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> > For additional commands, e-mail: dev-help@activemq.apache.org
> > For further information, visit: https://activemq.apache.org/contact
> >
> >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
By the way, just to clarify about the conventional commit message, it's a
suggestion, you are free to use it or not :)
Personally, I will force myself to do use it (to force myself to think
about the kind of changes I'm doing).
Regards
JB
On Thu, Feb 19, 2026 at 6:19 PM Jean-Louis Monteiro <
jlmonteiro@tomitribe.com> wrote:
> That looks great JB. Thanks for pushing on it.
> I'm sure we'll learn and adjust as we go along.
>
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org>
> wrote:
>
> > Thanks for all your efforts on this! It would be good to add a md file
> > with all this info and link it from the webpage and main README.md
> >
> > A couple of follow-ons:
> >
> > 1. I’m playing around with Milestones as a way to track long running
> > feature groups across version releases — ie JMS 3.0/2.1
> >
> > 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
> > this allows for better visibility across orgs and repos.
> >
> > 3. Projects allow us to link issues in dependencies in other orgs/repos
> > that fix things that we find or are related to a release for easier
> > discovery by end-users.
> >
> > More to come!
> >
> > Thanks,
> > Matt Pavlovich
> >
> > > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> > wrote:
> > >
> > > Hi folks,
> > >
> > > We are pleased to announce that GitHub Issues & Discussions.
> > >
> > > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > > Jira is now read-only and we should now all use GitHub Issues.
> > >
> > > We have the following labels available:
> > > - bug: for bug reports
> > > - dependencies: for dependencies updates
> > > - enhancement: for improvements on existing code
> > > - feature: for a complete new features
> > > - proposal: for a design proposal, big features
> > > - stale: when the issue is "inactive" for more than 60 days
> > >
> > > Please use these labels to classify the issues.
> > >
> > > When you create a PR, you can associate it with an issue either in the
> > > GitHub UI or using "This closes #xxxx" in the comments.
> > > I also suggest using conventional commit messages in PR with the
> > > format <type>(<scope>): <subject> where scope is optional. The type can
> > be:
> > > - feat: (a new feature is introduced with the changes)
> > > - fix: (bug fix has occurred, not a fix to a build script)
> > > - docs: (changes to the documentation)
> > > - style: (formatting, missing semicolons, etc; no production code
> change)
> > > - refactor: (refactoring production code, eg. renaming a variable)
> > > - test: (adding missing tests, refactoring tests; no production code
> > change)
> > > - chore: (changes that do not relate to a fix or feature and don't
> modify
> > > src or test files (for example updating dependencies or change in
> > > production code))
> > > - perf – (performance improvements)
> > > - ci – (continuous integration related)
> > > - build – (changes that affect the build system or external
> dependencies)
> > > - revert – (reverts a previous commit)
> > > That's a nice practice because GitHub can use that to create nice
> Release
> > > Notes.
> > > Thanks to that, it's not necessary to create GH issues for all changes.
> > >
> > > For versions, we are using GitHub Projects (
> > > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > > You can assign several projects/versions per issue, and track the
> status
> > of
> > > the versions.
> > >
> > > 2. GitHub Discussions
> > > We also enabled GitHub Discussions where we can have technical
> > discussions.
> > > The GH Discussions are automatically going to the dev@ mailing list.
> > >
> > > Let us know if you have any questions.
> > >
> > > Regards
> > > JB
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> > For additional commands, e-mail: dev-help@activemq.apache.org
> > For further information, visit: https://activemq.apache.org/contact
> >
> >
> >
>
Re: GitHub Issues & Discussions enabled
Posted by Jean-Louis Monteiro <jl...@tomitribe.com>.
That looks great JB. Thanks for pushing on it.
I'm sure we'll learn and adjust as we go along.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Thu, Feb 19, 2026 at 5:52 PM Matt Pavlovich <ma...@apache.org> wrote:
> Thanks for all your efforts on this! It would be good to add a md file
> with all this info and link it from the webpage and main README.md
>
> A couple of follow-ons:
>
> 1. I’m playing around with Milestones as a way to track long running
> feature groups across version releases — ie JMS 3.0/2.1
>
> 2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ —
> this allows for better visibility across orgs and repos.
>
> 3. Projects allow us to link issues in dependencies in other orgs/repos
> that fix things that we find or are related to a release for easier
> discovery by end-users.
>
> More to come!
>
> Thanks,
> Matt Pavlovich
>
> > On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
> >
> > Hi folks,
> >
> > We are pleased to announce that GitHub Issues & Discussions.
> >
> > 1. GitHub Issues (https://github.com/apache/activemq/issues)
> > Jira is now read-only and we should now all use GitHub Issues.
> >
> > We have the following labels available:
> > - bug: for bug reports
> > - dependencies: for dependencies updates
> > - enhancement: for improvements on existing code
> > - feature: for a complete new features
> > - proposal: for a design proposal, big features
> > - stale: when the issue is "inactive" for more than 60 days
> >
> > Please use these labels to classify the issues.
> >
> > When you create a PR, you can associate it with an issue either in the
> > GitHub UI or using "This closes #xxxx" in the comments.
> > I also suggest using conventional commit messages in PR with the
> > format <type>(<scope>): <subject> where scope is optional. The type can
> be:
> > - feat: (a new feature is introduced with the changes)
> > - fix: (bug fix has occurred, not a fix to a build script)
> > - docs: (changes to the documentation)
> > - style: (formatting, missing semicolons, etc; no production code change)
> > - refactor: (refactoring production code, eg. renaming a variable)
> > - test: (adding missing tests, refactoring tests; no production code
> change)
> > - chore: (changes that do not relate to a fix or feature and don't modify
> > src or test files (for example updating dependencies or change in
> > production code))
> > - perf – (performance improvements)
> > - ci – (continuous integration related)
> > - build – (changes that affect the build system or external dependencies)
> > - revert – (reverts a previous commit)
> > That's a nice practice because GitHub can use that to create nice Release
> > Notes.
> > Thanks to that, it's not necessary to create GH issues for all changes.
> >
> > For versions, we are using GitHub Projects (
> > https://github.com/apache/activemq/projects?query=is%3Aopen).
> > You can assign several projects/versions per issue, and track the status
> of
> > the versions.
> >
> > 2. GitHub Discussions
> > We also enabled GitHub Discussions where we can have technical
> discussions.
> > The GH Discussions are automatically going to the dev@ mailing list.
> >
> > Let us know if you have any questions.
> >
> > Regards
> > JB
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
> For additional commands, e-mail: dev-help@activemq.apache.org
> For further information, visit: https://activemq.apache.org/contact
>
>
>
Re: GitHub Issues & Discussions enabled
Posted by Matt Pavlovich <ma...@apache.org>.
Thanks for all your efforts on this! It would be good to add a md file with all this info and link it from the webpage and main README.md
A couple of follow-ons:
1. I’m playing around with Milestones as a way to track long running feature groups across version releases — ie JMS 3.0/2.1
2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ — this allows for better visibility across orgs and repos.
3. Projects allow us to link issues in dependencies in other orgs/repos that fix things that we find or are related to a release for easier discovery by end-users.
More to come!
Thanks,
Matt Pavlovich
> On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi folks,
>
> We are pleased to announce that GitHub Issues & Discussions.
>
> 1. GitHub Issues (https://github.com/apache/activemq/issues)
> Jira is now read-only and we should now all use GitHub Issues.
>
> We have the following labels available:
> - bug: for bug reports
> - dependencies: for dependencies updates
> - enhancement: for improvements on existing code
> - feature: for a complete new features
> - proposal: for a design proposal, big features
> - stale: when the issue is "inactive" for more than 60 days
>
> Please use these labels to classify the issues.
>
> When you create a PR, you can associate it with an issue either in the
> GitHub UI or using "This closes #xxxx" in the comments.
> I also suggest using conventional commit messages in PR with the
> format <type>(<scope>): <subject> where scope is optional. The type can be:
> - feat: (a new feature is introduced with the changes)
> - fix: (bug fix has occurred, not a fix to a build script)
> - docs: (changes to the documentation)
> - style: (formatting, missing semicolons, etc; no production code change)
> - refactor: (refactoring production code, eg. renaming a variable)
> - test: (adding missing tests, refactoring tests; no production code change)
> - chore: (changes that do not relate to a fix or feature and don't modify
> src or test files (for example updating dependencies or change in
> production code))
> - perf – (performance improvements)
> - ci – (continuous integration related)
> - build – (changes that affect the build system or external dependencies)
> - revert – (reverts a previous commit)
> That's a nice practice because GitHub can use that to create nice Release
> Notes.
> Thanks to that, it's not necessary to create GH issues for all changes.
>
> For versions, we are using GitHub Projects (
> https://github.com/apache/activemq/projects?query=is%3Aopen).
> You can assign several projects/versions per issue, and track the status of
> the versions.
>
> 2. GitHub Discussions
> We also enabled GitHub Discussions where we can have technical discussions.
> The GH Discussions are automatically going to the dev@ mailing list.
>
> Let us know if you have any questions.
>
> Regards
> JB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@activemq.apache.org
For additional commands, e-mail: dev-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
RE: GitHub Issues & Discussions enabled
Posted by Vilius Šumskas via dev <de...@activemq.apache.org>.
Nice!
Will all old Jira issues be migrated to GitHub too?
Also, I'm wondering, how "stale" issues will be managed? I would hate to see those bots automatically closing issues if they are "inactive". I understand that sometimes there is a need to manage a backlog, but this doesn't allow "voting" on issues with likes or other means of activity other than "me too, please reopen" comments.
--
Best Regards,
Vilius
-----Original Message-----
From: Jean-Baptiste Onofré <jb...@nanthrax.net>
Sent: Thursday, February 19, 2026 6:42 PM
To: dev@activemq.apache.org; users@activemq.apache.org
Subject: GitHub Issues & Discussions enabled
Hi folks,
We are pleased to announce that GitHub Issues & Discussions.
1. GitHub Issues (https://github.com/apache/activemq/issues)
Jira is now read-only and we should now all use GitHub Issues.
We have the following labels available:
- bug: for bug reports
- dependencies: for dependencies updates
- enhancement: for improvements on existing code
- feature: for a complete new features
- proposal: for a design proposal, big features
- stale: when the issue is "inactive" for more than 60 days
Please use these labels to classify the issues.
When you create a PR, you can associate it with an issue either in the GitHub UI or using "This closes #xxxx" in the comments.
I also suggest using conventional commit messages in PR with the format <type>(<scope>): <subject> where scope is optional. The type can be:
- feat: (a new feature is introduced with the changes)
- fix: (bug fix has occurred, not a fix to a build script)
- docs: (changes to the documentation)
- style: (formatting, missing semicolons, etc; no production code change)
- refactor: (refactoring production code, eg. renaming a variable)
- test: (adding missing tests, refactoring tests; no production code change)
- chore: (changes that do not relate to a fix or feature and don't modify src or test files (for example updating dependencies or change in production code))
- perf – (performance improvements)
- ci – (continuous integration related)
- build – (changes that affect the build system or external dependencies)
- revert – (reverts a previous commit)
That's a nice practice because GitHub can use that to create nice Release Notes.
Thanks to that, it's not necessary to create GH issues for all changes.
For versions, we are using GitHub Projects ( https://github.com/apache/activemq/projects?query=is%3Aopen).
You can assign several projects/versions per issue, and track the status of the versions.
2. GitHub Discussions
We also enabled GitHub Discussions where we can have technical discussions.
The GH Discussions are automatically going to the dev@ mailing list.
Let us know if you have any questions.
Regards
JB
Re: GitHub Issues & Discussions enabled
Posted by Matt Pavlovich <ma...@apache.org>.
Thanks for all your efforts on this! It would be good to add a md file with all this info and link it from the webpage and main README.md
A couple of follow-ons:
1. I’m playing around with Milestones as a way to track long running feature groups across version releases — ie JMS 3.0/2.1
2. Project names need to be fully qualified ‘Apache ActiveMQ v6.3.0’ — this allows for better visibility across orgs and repos.
3. Projects allow us to link issues in dependencies in other orgs/repos that fix things that we find or are related to a release for easier discovery by end-users.
More to come!
Thanks,
Matt Pavlovich
> On Feb 19, 2026, at 10:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> Hi folks,
>
> We are pleased to announce that GitHub Issues & Discussions.
>
> 1. GitHub Issues (https://github.com/apache/activemq/issues)
> Jira is now read-only and we should now all use GitHub Issues.
>
> We have the following labels available:
> - bug: for bug reports
> - dependencies: for dependencies updates
> - enhancement: for improvements on existing code
> - feature: for a complete new features
> - proposal: for a design proposal, big features
> - stale: when the issue is "inactive" for more than 60 days
>
> Please use these labels to classify the issues.
>
> When you create a PR, you can associate it with an issue either in the
> GitHub UI or using "This closes #xxxx" in the comments.
> I also suggest using conventional commit messages in PR with the
> format <type>(<scope>): <subject> where scope is optional. The type can be:
> - feat: (a new feature is introduced with the changes)
> - fix: (bug fix has occurred, not a fix to a build script)
> - docs: (changes to the documentation)
> - style: (formatting, missing semicolons, etc; no production code change)
> - refactor: (refactoring production code, eg. renaming a variable)
> - test: (adding missing tests, refactoring tests; no production code change)
> - chore: (changes that do not relate to a fix or feature and don't modify
> src or test files (for example updating dependencies or change in
> production code))
> - perf – (performance improvements)
> - ci – (continuous integration related)
> - build – (changes that affect the build system or external dependencies)
> - revert – (reverts a previous commit)
> That's a nice practice because GitHub can use that to create nice Release
> Notes.
> Thanks to that, it's not necessary to create GH issues for all changes.
>
> For versions, we are using GitHub Projects (
> https://github.com/apache/activemq/projects?query=is%3Aopen).
> You can assign several projects/versions per issue, and track the status of
> the versions.
>
> 2. GitHub Discussions
> We also enabled GitHub Discussions where we can have technical discussions.
> The GH Discussions are automatically going to the dev@ mailing list.
>
> Let us know if you have any questions.
>
> Regards
> JB
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@activemq.apache.org
For additional commands, e-mail: users-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact