Hello, So, creating this is no big trouble ... but, if we can merge it soon after 3.20, then I think it may be OK to wait. That way we can reuse the automation we already have in place/
IMHO, I think the most important bit is to avoid a sudden huge spike in failed tests. As we'll have a lot of activity going on, it may become difficult to bisect to find and fix issues. So, it's good to do QA from the beginning trying to contain and fix the failures as they emerge. Kind regards On Sat, Nov 26, 2022 at 10:24 AM Claus Ibsen <[email protected]> wrote: > Hi > > After the 3.20 LTS release (next month in a few weeks) then we can cross > over and make the main branch for Camel v4. > I am just wonder if we then need to setup temporary stuff at all, or can go > on until 3.20 is released (eg we can start earlier when the VOTE starts and > we have a tag in git). > > > On Sat, Nov 26, 2022 at 8:47 AM Otavio Rodolfo Piske <[email protected] > > > wrote: > > > Hello, > > > > This looks cool. Please let me know if you would like some help setting > up > > the github actions. We have some of them that you can use as a starting > > point and maybe you can tweak them for that. > > > > If you believe these branches are going to be active for a while, there's > > another thing you might want to consider: adding a CI job for that. We > > should be able to add one in our CI at Apache. I can also give you some > > pointers for that. > > > > Kind regards > > > > On Fri, Nov 25, 2022 at 10:15 PM Guillaume Nodet <[email protected]> > > wrote: > > > > > I've begun working on the Jakarta 10 migration. > > > I tried with a 4.x branch [1], but it's difficult to maintain with the > > > number of commits in the main branch. So I decided to switch to a > > > different mechanism. > > > I've created several branches upstream : > > > * jakarta-rewrite [2] : contains a migration shell script [3] to be > > > executed regularly (I'll try to setup a github action at some point in > > the > > > near future). This scripts uses perl regular expressions and git to > > > perform most of the upgrade. When executed, the script will first > rebase > > > on top of the main branch, run the migration and force push to the > > > jakarta-rewritten branch > > > * jakarta-rewritten [4] : contains the migrated code. The idea is to > > have > > > it regularly and automatically updated and run to have an idea of the > > > current state. It's not yet buildable ! > > > * jarkarta-jetty [5] : contains one commit [6] to be merged as part > of > > > the migration executed by the script [7]. Other branches may be set up > > as > > > needed. Those are used for things that can't be done with simple shell > > > commands. > > > > > > I'll keep you posted ! > > > > > > Cheers, > > > Guillaume > > > > > > [1] https://github.com/apache/camel/pull/8579 > > > [2] https://github.com/apache/camel/tree/jakarta-rewrite > > > [3] > > > > > > https://github.com/apache/camel/blob/jakarta-rewrite/jakarta/transform.sh > > > [4] https://github.com/apache/camel/tree/jakarta-rewritten > > > [5] https://github.com/apache/camel/tree/jakarta-jetty > > > [6] > > > > > > > > > https://github.com/apache/camel/commit/e5aea792291557b86b10eb84b978b381c2d94be6 > > > [7] > > > > > > > > > https://github.com/apache/camel/blob/8c60590d18542665e5048780f674d499f900c604/jakarta/transform.sh#L224 > > > > > > ------------------------ > > > Guillaume Nodet > > > > > > > > > -- > > Otavio R. Piske > > http://orpiske.net > > > > > -- > Claus Ibsen > ----------------- > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Otavio R. Piske http://orpiske.net
