A little late but thought I’d put in my $0.02 +1 for GitHub issues. There are APIs avail to migrate, so I”m not super concerned about lock-in.
Also, there is thing saying we can’t use GH actions and Apache Jenkins CI at the same time. GH actions seem to have more runner nodes vs Apache Jenkins infra and are great for when there are a lot of PR’s lined up. I use both GH Actions and Jenkins for jaxb-tools. -Matt > On Feb 5, 2024, at 12:56 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > > Hi, > > Yeeah, that would help. As said, my priority is the 4.5.0 release this > week. The move to GH will happen after. > > Thanks ! > Regards > JB > > On Mon, Feb 5, 2024 at 7:33 AM Grzegorz Grzybek <gr.grzy...@gmail.com> wrote: >> >> Hello >> >> JBO - we can discuss on slack later if you decide to migrate - we can use >> the scripts I used to migrate Pax projects. >> >> regards >> Grzegorz Grzybek >> >> sob., 3 lut 2024 o 06:39 Jean-Baptiste Onofré <j...@nanthrax.net> napisał(a): >>> >>> Hi guys, >>> >>> it seems we have a consensus here. >>> >>> I propose to complete Karaf 4.5.0 release first and then I will move >>> forward on the switch to GH Issues (and also GH Actions). >>> >>> Thanks, >>> Regards >>> JB >>> >>> On Tue, Oct 31, 2023 at 9:27 AM Jean-Baptiste Onofré <j...@nanthrax.net> >>> wrote: >>>> >>>> Hi guys, >>>> >>>> I would like to propose to move from Jira to GH Issues and from >>>> Jenkins to GH Actions. >>>> >>>> As we have several sub-projects, each sub-project will have its own >>>> space, like we do for Karaf Minho >>>> (https://github.com/apache/karaf-minho). >>>> >>>> The migration should be "smooth" and I will work on it if you agree. >>>> >>>> Thoughts ? >>>> >>>> Regards >>>> JB
