Hi folks,

Since a -1 only acts as a veto for code modifications, this vote is
considered a governance and procedural matter. Therefore, it follows a
simple majority rule.

The final results are:

+1: 9 votes
-1: 1 vote

Based on this result, I propose we move forward with the migration from
Jira to GitHub Issues following the ActiveMQ 6.2.1 release.

Regards,
JB

On Tue, Dec 16, 2025 at 7:56 PM Jean-Baptiste Onofré <[email protected]>
wrote:

> Hi folks,
>
> Following our previous discussions, I am calling a formal vote on the
> proposal to migrate from Jira to GitHub Issues.
>
> This topic has been discussed extensively over the past few months. For
> context, please review the following threads outlining the pros and cons:
>
> - https://lists.apache.org/thread/w3cl57zs7xmhk38mpzygp29whmmdbjkw
> - https://lists.apache.org/thread/zqp72y8jpsc4q9g9z4skxjyozxs8gr8r
> - https://lists.apache.org/thread/9ryfs0y8gnl2z4o2d7q646ffdrs9zzcp
> - https://lists.apache.org/thread/93v6b5xxmthsypcwgvhotsmm4y2whdkm
> -
> https://github.com/jbertram/activemq-website/wiki/Apache-ActiveMQ-GitHub-Issues-Migration-Review
>
> I would like to gauge the community's support on this topic. Please cast
> your vote on the adoption of GitHub Issues instead of Jira:
>
> [ ] +1 Approve: Migrate to GitHub Issues.
> [ ] 0 Neutral: I don't care, or I will abstain.
> [ ] -1 Disapprove: Do not approve the migration (Please provide specific
> reasons for your objection).
>
> The vote will remain open for the next 72 hours.
>
> Thanks,
> Regards
> JB
>

Reply via email to