Fair point.
My proposal (as explained in a previous message) is to move ActiveMQ
first, and then the rest.
Of course if the community agrees (PMC members with the input from
users/contributors).
I'm focusing on ActiveMQ 6.0.0 right now, but it would be good to have
a consensus just after.
I've thought about this some more and I think we should probably be
consistent with all projects.
Justin has made a good point about there being 21 projects/repos. I think
the switch would be fine to GH issues, but if we did it I think we should
be consistent and have all projects managed the
Yes, my point was we have the same features as base.
For me, the key differences are:
1. User management, authentication, and span handling
2. Better integration with PR and Actions/Workflows
3. Release/version handling is probably better on Jira, but GH Issues
milestone support is sufficient for
About the features Github also have projects, roadmap, kanban
I cannot see which features are missing for the common ASF projects.
On 18/10/2023 11:40, Jean-Baptiste Onofré wrote:
The opposite is also true: why not move as we have the same features
That's true Jira has much more features
Hi guys,
A quick update about ActiveMQ 6.0.0.
I fixed the issues detected, I will open the corresponding PRs soon.
The target date to submit the release to vote is the end of this week.
I will keep you posted.
Regards
JB
On Mon, Oct 2, 2023 at 7:44 AM Jean-Baptiste Onofré wrote:
>
> Hi
Hi
On Wed, Oct 18, 2023 at 6:41 AM Justin Bertram wrote:
>
> > Correct, it's two "isolated" Jira spaces.
>
> We have four distinct Jira projects:
> - https://issues.apache.org/jira/projects/AMQ
> - https://issues.apache.org/jira/projects/ARTEMIS
> -
