I prefer Jira for issue tracking, I think it's better at it, particularly for cases like 5.x / 6.x having multiple active release streams with lots of backports, given the limitations of Milestone handling and how people tend to treat xref'ing to fully compensate for that (i.e they often dont bother).
I would be fine with adopting Issues too though, I use Issues plenty elsewhere where it's enabled by default and the only option anyway hehe. I expect most users reporting things would prefer Issues at this point, especially anyone intende to raise a PR, and most particularly all the folks without Jira accounts already (of course, I also think many of those asking for accounts dont actually need one; see Discussions note at end). I dont actually think every component needs to use the exact same labels etc. People are already used to just about every other GitHub repo they encounter at this point which uses Issue having their own labels. For me, the labels just need to make sense in themselves. Though the default ones are simple, so I'd be fine with them, which would then just happen to be consistent. It's not clear to me anyone proposing to move to Issues actually intended thus far to migrate any of the [open] issues from Jira to Github Issues, so much as just start using Github Issues and thus effectively 'clearing the cruft' by leaving it where it is, then raising new issues going forward? To the later point around Discussions, I do think enabling those could be good either way since, just like with Jira, people will often create Issues to ask questions rather than e.g mail a mailing list. They might use a Discussion instead though. On Tue, 2 Apr 2024 at 20:52, Justin Bertram <jbert...@apache.org> wrote: > > There's been a few threads about this general subject, but most have > concentrated on Classic in particular. I think it's worth discussing > migration of ActiveMQ as a whole and diving a bit deeper into the details > of why a migration makes (or doesn't make) sense and what the challenges > may be. > > To this end I've put together this document [1]. I hope it will be of > service to the community as we consider this option. > > > Justin > > [1] > https://github.com/jbertram/activemq-website/wiki/Apache-ActiveMQ-GitHub-Issues-Migration-Review
