It may be better to break this up into separate [DISCUSS] threads - one for
Apache Jenkins and GitHub Actions and one for Apache Jira and GitHub Issues.

In any event, it would be good to get clear details on a few different
points:

 - What specifically are the problems with the existing solution?
 - How are those problems addressed by the proposed solution? Are there
additional features in the proposed solution that will enable new
opportunities that don't currently exist?
 - What are the risks of migrating?
 - What is the migration plan?

Once these details are clear we will be able to make an informed decision
about what action we should take.

Lastly, I think these issues should be considered across ActiveMQ as a
whole and not just for any individual component. I believe that having
different ways of doing the same thing for different components on the same
project is going to be confusing and frustrating for users and developers
alike.


Justin

On Fri, Oct 13, 2023 at 11:13 AM Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi guys,
>
> Even if we are pretty busy and focused on ActiveMQ 6.0.0 release
> preparation (as said in another email, I should be able to submit the
> release to vote next week), I think we can anticipate a little the
> future of ActiveMQ.
> ActiveMQ 6.0.0 is a major milestone for the project, heading to a more
> modern approach (I started a PoC to remove Spring dep and using SPI
> like approach at broker side, I will keep you posted about that) for
> the codebase, website, and our developer experience.
>
> I would like to discuss:
> 1. Moving from Apache Jenkins to GitHub Actions, using multiple
> workflows, more decoupled, with potentially more "executors" to build
> and leveraging GitHub Actions "modules".
> 2. Moving from Apache Jira to GitHub Issues. Several Apache projects
> already use GitHub Issues. At OPS4J we also migrated from Jira to GH
> Issues. We were able to import everything from Jira without losing
> data. I think it would also be a good opportunity to do some cleanup,
> maybe starting with only tickets for 6.x.
>
> Thoughts ?
>
> Regards
> JB
>
>

Reply via email to