-1 I don't think there's been sufficient discussion of the pros and cons to make an informed decision. I've done some investigation and testing and I'd like a chance to present my findings. This would be a fairly significant change, and I think it deserves a more detailed review than we've had so far.
Also, I think migration should be considered for ActiveMQ as a whole and not just a single component (i.e. Classic). Having multiple different ways to complete the same task in the same project isn't going to be great for users or contributors. If the change is good for one component then it stands to reason that it would be good for all. Justin On Fri, Mar 15, 2024 at 10:06 AM Matt Pavlovich <mattr...@gmail.com> wrote: > All- > > Kicking off a vote thread for migrating ActiveMQ Classic issues from JIRA > to GitHub. > > This vote covers: > - Migration of ActiveMQ Classic JIRA issues to GitHub > - Update Apache ActiveMQ website with links to GitHub issues > > This vote will be open for at least 72 hours. > > Thank you, > Matt Pavlovich > >
