Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
On Thu, Jan 12, 2023 at 2:44 PM Jean-Baptiste Onofré wrote: > As already discussed, I will move forward on Camel-Karaf to > Karaf-Camel (I will ping you on zulip channel about that). > > Thanks for stepping up and moving the code over to karaf to its new osgi based home > Regards > JB > > On Wed, Jan 11, 2023 at 9:34 AM Andrea Cosentino > wrote: > > > > Branches have been created. > > > > CI jobs should updated. > > > > I guess we need to aling the regen action for 3.x, by pointing to the > new branches. > > > > If something is missing, please report. > > > > Thanks > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > wrote: > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > Once they are, we could create the branches. > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > Hi > > > > Lets try to get ready this week for switching main to v4. > > Guillaume is back from PTO and will prepare his work today so it can be > > ready for the switch. > > In the meantime we need to prepare for the switch. > > > > We need to setup branches for v3 as its "main" branch. > > - camel-3.x > > - camel-spring-boot-3.x > > - camel-karaf-3.x > > > > And have ASF CI servers able to build and test these branches (as it does > > today via main branch). > > This allows Camel v3 to continue as is, as we need to keep maintaining it > > till the end of 2023. > > > > When we have these branches, then we need to remember to backport commits > > to these branches as well, > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that > > backporting commits is now potentially more branches: > > > > main > > camel-3.x > > camel-3.20.x > > camel-3.18.x > > camel-3.14.x > > > > It may be that before making the switch then Guillaume needs the "main" > > branch to not have new commits for a couple of hours. > > If so then lets us know Guillaume, as we can in the mean time then send > > only work as PRs and then apply these after the switch. > > > > However when you are getting closer to make the switch then give us a > heads > > up here in this mail thread, thanks. > > > > > > > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen > wrote: > > > > > Hi > > > > > > The work on Camel v4 is starting and we will publish a blog post on the > > > roadmap and timeline for Camel v4 later this week. > > > > > > Some time next week we would like to switch "main" branch to v4, and > then > > > create a new camel-3.x branch as the active branch for future Camel v3 > > > releases (next will be 3.21). > > > > > > The v4 is work in progress and in the beginning there will be plenty of > > > stuff that fail tests, and components disabled as they have not yet > been > > > migrated to jakarta spec etc. So when we have the main branch switched > then > > > more people can help with this work - where we can work on a per > component > > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > > > > > -- > > > Claus Ibsen > > > - > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
As already discussed, I will move forward on Camel-Karaf to Karaf-Camel (I will ping you on zulip channel about that). Regards JB On Wed, Jan 11, 2023 at 9:34 AM Andrea Cosentino wrote: > > Branches have been created. > > CI jobs should updated. > > I guess we need to aling the regen action for 3.x, by pointing to the new > branches. > > If something is missing, please report. > > Thanks > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > wrote: > > > > > > There are some pending PRs waiting to be merged. > > Once they are, we could create the branches. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen > wrote: > > > > > > Hi > > Lets try to get ready this week for switching main to v4. > Guillaume is back from PTO and will prepare his work today so it can be > ready for the switch. > In the meantime we need to prepare for the switch. > > We need to setup branches for v3 as its "main" branch. > - camel-3.x > - camel-spring-boot-3.x > - camel-karaf-3.x > > And have ASF CI servers able to build and test these branches (as it does > today via main branch). > This allows Camel v3 to continue as is, as we need to keep maintaining it > till the end of 2023. > > When we have these branches, then we need to remember to backport commits > to these branches as well, > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that > backporting commits is now potentially more branches: > > main > camel-3.x > camel-3.20.x > camel-3.18.x > camel-3.14.x > > It may be that before making the switch then Guillaume needs the "main" > branch to not have new commits for a couple of hours. > If so then lets us know Guillaume, as we can in the mean time then send > only work as PRs and then apply these after the switch. > > However when you are getting closer to make the switch then give us a heads > up here in this mail thread, thanks. > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen wrote: > > > Hi > > > > The work on Camel v4 is starting and we will publish a blog post on the > > roadmap and timeline for Camel v4 later this week. > > > > Some time next week we would like to switch "main" branch to v4, and then > > create a new camel-3.x branch as the active branch for future Camel v3 > > releases (next will be 3.21). > > > > The v4 is work in progress and in the beginning there will be plenty of > > stuff that fail tests, and components disabled as they have not yet been > > migrated to jakarta spec etc. So when we have the main branch switched then > > more people can help with this work - where we can work on a per component > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
It's a different problem. The module was skipped and btw this a switch to a bigger refactor related to move to Camel 4.x, so hiccups is expected. Il giorno mer 11 gen 2023 alle ore 12:01 Christofer Dutz < christofer.d...@c-ware.de> ha scritto: > This was exactly what I noticed when reviewing the RC for the 3.20.0 > release. > > I think I even left some comments on how to fix the problems. > > In this case I think the integration-tests failed because the pom in the > test referenced artifacts that weren’t built yet. > A simple fix should be to simply add these dependencies as test > dependencies to the pom of the module doing the test. > Then Maven will ensure it’s built before trying to run the tests. > > Chris > > From: Andrea Cosentino > Date: Wednesday, 11. January 2023 at 11:47 > To: dev@camel.apache.org > Subject: Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in > 2023) > If you run it from the beginning with a clean m2 repo, you'll get this > > [ERROR] Failed to execute goal on project camel-servlet: Could not resolve > dependencies for project org.apache.camel:camel-servlet:jar:4.0.0-SNAPSHOT: > Could not find artifact > org.apache.camel:camel-swagger-java:jar:4.0.0-SNAPSHOT in apache-public ( > https://repository.apache.org/content/groups/public/) -> [Help 1] > > This is because camel-swagger-java needs to be before camel-servlet > > Il giorno mer 11 gen 2023 alle ore 11:36 Claus Ibsen < > claus.ib...@gmail.com> > ha scritto: > > > Hi > > > > The main branch is now v4 and this means you must use Java 17 to compile > > the code. > > > > > > > > On Wed, Jan 11, 2023 at 11:06 AM Guillaume Nodet > > wrote: > > > > > I pushed the changes. > > > > > > Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a > > > écrit : > > > > > > > Hi > > > > > > > > Guillaume is ready for pushing v4 to main branch. So he is doing this > > > now. > > > > Until he is done then please do not commit directly to main, but only > > do > > > > PRs > > > > > > > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > > > > wrote: > > > > > > > > > Branches have been created. > > > > > > > > > > CI jobs should updated. > > > > > > > > > > I guess we need to aling the regen action for 3.x, by pointing to > the > > > new > > > > > branches. > > > > > > > > > > If something is missing, please report. > > > > > > > > > > Thanks > > > > > > > > > > -- > > > > > Andrea Cosentino > > > > > -- > > > > > Apache Camel PMC Chair > > > > > Apache Karaf Committer > > > > > Apache Servicemix PMC Member > > > > > Email: ancosen1...@yahoo.com > > > > > Twitter: @oscerd2 > > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > > > > > > > Once they are, we could create the branches. > > > > > > > > > > -- > > > > > Andrea Cosentino > > > > > -- > > > > > Apache Camel PMC Chair > > > > > Apache Karaf Committer > > > > > Apache Servicemix PMC Member > > > > > Email: ancosen1...@yahoo.com > > > > > Twitter: @oscerd2 > > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > > > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > Lets try to get ready this week for switching main to v4. > > > > > Guillaume is back from PTO and will prepare his work today so it > can > > be >
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
This was exactly what I noticed when reviewing the RC for the 3.20.0 release. I think I even left some comments on how to fix the problems. In this case I think the integration-tests failed because the pom in the test referenced artifacts that weren’t built yet. A simple fix should be to simply add these dependencies as test dependencies to the pom of the module doing the test. Then Maven will ensure it’s built before trying to run the tests. Chris From: Andrea Cosentino Date: Wednesday, 11. January 2023 at 11:47 To: dev@camel.apache.org Subject: Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023) If you run it from the beginning with a clean m2 repo, you'll get this [ERROR] Failed to execute goal on project camel-servlet: Could not resolve dependencies for project org.apache.camel:camel-servlet:jar:4.0.0-SNAPSHOT: Could not find artifact org.apache.camel:camel-swagger-java:jar:4.0.0-SNAPSHOT in apache-public ( https://repository.apache.org/content/groups/public/) -> [Help 1] This is because camel-swagger-java needs to be before camel-servlet Il giorno mer 11 gen 2023 alle ore 11:36 Claus Ibsen ha scritto: > Hi > > The main branch is now v4 and this means you must use Java 17 to compile > the code. > > > > On Wed, Jan 11, 2023 at 11:06 AM Guillaume Nodet > wrote: > > > I pushed the changes. > > > > Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a > > écrit : > > > > > Hi > > > > > > Guillaume is ready for pushing v4 to main branch. So he is doing this > > now. > > > Until he is done then please do not commit directly to main, but only > do > > > PRs > > > > > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > > > wrote: > > > > > > > Branches have been created. > > > > > > > > CI jobs should updated. > > > > > > > > I guess we need to aling the regen action for 3.x, by pointing to the > > new > > > > branches. > > > > > > > > If something is missing, please report. > > > > > > > > Thanks > > > > > > > > -- > > > > Andrea Cosentino > > > > -- > > > > Apache Camel PMC Chair > > > > Apache Karaf Committer > > > > Apache Servicemix PMC Member > > > > Email: ancosen1...@yahoo.com > > > > Twitter: @oscerd2 > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > > > > > Once they are, we could create the branches. > > > > > > > > -- > > > > Andrea Cosentino > > > > -- > > > > Apache Camel PMC Chair > > > > Apache Karaf Committer > > > > Apache Servicemix PMC Member > > > > Email: ancosen1...@yahoo.com > > > > Twitter: @oscerd2 > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > Lets try to get ready this week for switching main to v4. > > > > Guillaume is back from PTO and will prepare his work today so it can > be > > > > ready for the switch. > > > > In the meantime we need to prepare for the switch. > > > > > > > > We need to setup branches for v3 as its "main" branch. > > > > - camel-3.x > > > > - camel-spring-boot-3.x > > > > - camel-karaf-3.x > > > > > > > > And have ASF CI servers able to build and test these branches (as it > > does > > > > today via main branch). > > > > This allows Camel v3 to continue as is, as we need to keep > maintaining > > it > > > > till the end of 2023. > > > > > > > > When we have these branches, then we need to remember to backport > > commits > > > > to these branches as well, > > > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means &g
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Yeah, Just noticed that. Sorry about the wrong information. Il giorno mer 11 gen 2023 alle ore 11:54 Guillaume Nodet ha scritto: > It's actually a bit more than that, as this component has been disabled in > the build. > Let me re-enable it. > > Le mer. 11 janv. 2023 à 11:47, Andrea Cosentino a > écrit : > > > If you run it from the beginning with a clean m2 repo, you'll get this > > > > [ERROR] Failed to execute goal on project camel-servlet: Could not > resolve > > dependencies for project > org.apache.camel:camel-servlet:jar:4.0.0-SNAPSHOT: > > Could not find artifact > > org.apache.camel:camel-swagger-java:jar:4.0.0-SNAPSHOT in apache-public ( > > https://repository.apache.org/content/groups/public/) -> [Help 1] > > > > This is because camel-swagger-java needs to be before camel-servlet > > > > Il giorno mer 11 gen 2023 alle ore 11:36 Claus Ibsen < > > claus.ib...@gmail.com> > > ha scritto: > > > > > Hi > > > > > > The main branch is now v4 and this means you must use Java 17 to > compile > > > the code. > > > > > > > > > > > > On Wed, Jan 11, 2023 at 11:06 AM Guillaume Nodet > > > wrote: > > > > > > > I pushed the changes. > > > > > > > > Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a > > > > écrit : > > > > > > > > > Hi > > > > > > > > > > Guillaume is ready for pushing v4 to main branch. So he is doing > this > > > > now. > > > > > Until he is done then please do not commit directly to main, but > only > > > do > > > > > PRs > > > > > > > > > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > > > > > wrote: > > > > > > > > > > > Branches have been created. > > > > > > > > > > > > CI jobs should updated. > > > > > > > > > > > > I guess we need to aling the regen action for 3.x, by pointing to > > the > > > > new > > > > > > branches. > > > > > > > > > > > > If something is missing, please report. > > > > > > > > > > > > Thanks > > > > > > > > > > > > -- > > > > > > Andrea Cosentino > > > > > > -- > > > > > > Apache Camel PMC Chair > > > > > > Apache Karaf Committer > > > > > > Apache Servicemix PMC Member > > > > > > Email: ancosen1...@yahoo.com > > > > > > Twitter: @oscerd2 > > > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea > Cosentino > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > > > > > > > > > Once they are, we could create the branches. > > > > > > > > > > > > -- > > > > > > Andrea Cosentino > > > > > > -- > > > > > > Apache Camel PMC Chair > > > > > > Apache Karaf Committer > > > > > > Apache Servicemix PMC Member > > > > > > Email: ancosen1...@yahoo.com > > > > > > Twitter: @oscerd2 > > > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > > > > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > Lets try to get ready this week for switching main to v4. > > > > > > Guillaume is back from PTO and will prepare his work today so it > > can > > > be > > > > > > ready for the switch. > > > > > > In the meantime we need to prepare for the switch. > > > > > > > > > > > > We need to setup branches for v3 as its "main" branch. > > > > > > - camel-3.x > > > > > > - camel-spring-boot-3.x > > > > > > - camel-karaf-3.x > > > > > > > > > > > > And have ASF CI servers able to build and test these branches (as > > it > > > > does > > > > > > today via main branch). > > > > > > This allows Camel v3 to continue as is, as we need to keep > > > maintaining > > > > it > > > > > > till the end of 2023. > > > > > > > > > > > > When we have these branches, then we need to remember to backport > > > > commits > > > > > > to these branches as well, > > > > > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This > means > > > that > > > > > > backporting commits is now potentially more branches: > > > > > > > > > > > > main > > > > > > camel-3.x > > > > > > camel-3.20.x > > > > > > camel-3.18.x > > > > > > camel-3.14.x > > > > > > > > > > > > It may be that before making the switch then Guillaume needs the > > > "main" > > > > > > branch to not have new commits for a couple of hours. > > > > > > If so then lets us know Guillaume, as we can in the mean time > then > > > send > > > > > > only work as PRs and then apply these after the switch. > > > > > > > > > > > > However when you are getting closer to make the switch then give > > us a > > > > > heads > > > > > > up here in this mail thread, thanks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen < > claus.ib...@gmail.com > > > > > > > > wrote: > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > The
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
It's actually a bit more than that, as this component has been disabled in the build. Let me re-enable it. Le mer. 11 janv. 2023 à 11:47, Andrea Cosentino a écrit : > If you run it from the beginning with a clean m2 repo, you'll get this > > [ERROR] Failed to execute goal on project camel-servlet: Could not resolve > dependencies for project org.apache.camel:camel-servlet:jar:4.0.0-SNAPSHOT: > Could not find artifact > org.apache.camel:camel-swagger-java:jar:4.0.0-SNAPSHOT in apache-public ( > https://repository.apache.org/content/groups/public/) -> [Help 1] > > This is because camel-swagger-java needs to be before camel-servlet > > Il giorno mer 11 gen 2023 alle ore 11:36 Claus Ibsen < > claus.ib...@gmail.com> > ha scritto: > > > Hi > > > > The main branch is now v4 and this means you must use Java 17 to compile > > the code. > > > > > > > > On Wed, Jan 11, 2023 at 11:06 AM Guillaume Nodet > > wrote: > > > > > I pushed the changes. > > > > > > Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a > > > écrit : > > > > > > > Hi > > > > > > > > Guillaume is ready for pushing v4 to main branch. So he is doing this > > > now. > > > > Until he is done then please do not commit directly to main, but only > > do > > > > PRs > > > > > > > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > > > > wrote: > > > > > > > > > Branches have been created. > > > > > > > > > > CI jobs should updated. > > > > > > > > > > I guess we need to aling the regen action for 3.x, by pointing to > the > > > new > > > > > branches. > > > > > > > > > > If something is missing, please report. > > > > > > > > > > Thanks > > > > > > > > > > -- > > > > > Andrea Cosentino > > > > > -- > > > > > Apache Camel PMC Chair > > > > > Apache Karaf Committer > > > > > Apache Servicemix PMC Member > > > > > Email: ancosen1...@yahoo.com > > > > > Twitter: @oscerd2 > > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > > > > > > > Once they are, we could create the branches. > > > > > > > > > > -- > > > > > Andrea Cosentino > > > > > -- > > > > > Apache Camel PMC Chair > > > > > Apache Karaf Committer > > > > > Apache Servicemix PMC Member > > > > > Email: ancosen1...@yahoo.com > > > > > Twitter: @oscerd2 > > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > > > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > Lets try to get ready this week for switching main to v4. > > > > > Guillaume is back from PTO and will prepare his work today so it > can > > be > > > > > ready for the switch. > > > > > In the meantime we need to prepare for the switch. > > > > > > > > > > We need to setup branches for v3 as its "main" branch. > > > > > - camel-3.x > > > > > - camel-spring-boot-3.x > > > > > - camel-karaf-3.x > > > > > > > > > > And have ASF CI servers able to build and test these branches (as > it > > > does > > > > > today via main branch). > > > > > This allows Camel v3 to continue as is, as we need to keep > > maintaining > > > it > > > > > till the end of 2023. > > > > > > > > > > When we have these branches, then we need to remember to backport > > > commits > > > > > to these branches as well, > > > > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means > > that > > > > > backporting commits is now potentially more branches: > > > > > > > > > > main > > > > > camel-3.x > > > > > camel-3.20.x > > > > > camel-3.18.x > > > > > camel-3.14.x > > > > > > > > > > It may be that before making the switch then Guillaume needs the > > "main" > > > > > branch to not have new commits for a couple of hours. > > > > > If so then lets us know Guillaume, as we can in the mean time then > > send > > > > > only work as PRs and then apply these after the switch. > > > > > > > > > > However when you are getting closer to make the switch then give > us a > > > > heads > > > > > up here in this mail thread, thanks. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen > > > > > wrote: > > > > > > > > > > > Hi > > > > > > > > > > > > The work on Camel v4 is starting and we will publish a blog post > on > > > the > > > > > > roadmap and timeline for Camel v4 later this week. > > > > > > > > > > > > Some time next week we would like to switch "main" branch to v4, > > and > > > > then > > > > > > create a new camel-3.x branch as the active branch for future > Camel > > > v3 > > > > > > releases (next will be 3.21). > > > > > > > > > > > > The v4 is work in progress and in the beginning there will be > > plenty > > > of > > > > > > stuff that
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
If you run it from the beginning with a clean m2 repo, you'll get this [ERROR] Failed to execute goal on project camel-servlet: Could not resolve dependencies for project org.apache.camel:camel-servlet:jar:4.0.0-SNAPSHOT: Could not find artifact org.apache.camel:camel-swagger-java:jar:4.0.0-SNAPSHOT in apache-public ( https://repository.apache.org/content/groups/public/) -> [Help 1] This is because camel-swagger-java needs to be before camel-servlet Il giorno mer 11 gen 2023 alle ore 11:36 Claus Ibsen ha scritto: > Hi > > The main branch is now v4 and this means you must use Java 17 to compile > the code. > > > > On Wed, Jan 11, 2023 at 11:06 AM Guillaume Nodet > wrote: > > > I pushed the changes. > > > > Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a > > écrit : > > > > > Hi > > > > > > Guillaume is ready for pushing v4 to main branch. So he is doing this > > now. > > > Until he is done then please do not commit directly to main, but only > do > > > PRs > > > > > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > > > wrote: > > > > > > > Branches have been created. > > > > > > > > CI jobs should updated. > > > > > > > > I guess we need to aling the regen action for 3.x, by pointing to the > > new > > > > branches. > > > > > > > > If something is missing, please report. > > > > > > > > Thanks > > > > > > > > -- > > > > Andrea Cosentino > > > > -- > > > > Apache Camel PMC Chair > > > > Apache Karaf Committer > > > > Apache Servicemix PMC Member > > > > Email: ancosen1...@yahoo.com > > > > Twitter: @oscerd2 > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > > > > > Once they are, we could create the branches. > > > > > > > > -- > > > > Andrea Cosentino > > > > -- > > > > Apache Camel PMC Chair > > > > Apache Karaf Committer > > > > Apache Servicemix PMC Member > > > > Email: ancosen1...@yahoo.com > > > > Twitter: @oscerd2 > > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > Lets try to get ready this week for switching main to v4. > > > > Guillaume is back from PTO and will prepare his work today so it can > be > > > > ready for the switch. > > > > In the meantime we need to prepare for the switch. > > > > > > > > We need to setup branches for v3 as its "main" branch. > > > > - camel-3.x > > > > - camel-spring-boot-3.x > > > > - camel-karaf-3.x > > > > > > > > And have ASF CI servers able to build and test these branches (as it > > does > > > > today via main branch). > > > > This allows Camel v3 to continue as is, as we need to keep > maintaining > > it > > > > till the end of 2023. > > > > > > > > When we have these branches, then we need to remember to backport > > commits > > > > to these branches as well, > > > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means > that > > > > backporting commits is now potentially more branches: > > > > > > > > main > > > > camel-3.x > > > > camel-3.20.x > > > > camel-3.18.x > > > > camel-3.14.x > > > > > > > > It may be that before making the switch then Guillaume needs the > "main" > > > > branch to not have new commits for a couple of hours. > > > > If so then lets us know Guillaume, as we can in the mean time then > send > > > > only work as PRs and then apply these after the switch. > > > > > > > > However when you are getting closer to make the switch then give us a > > > heads > > > > up here in this mail thread, thanks. > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen > > > wrote: > > > > > > > > > Hi > > > > > > > > > > The work on Camel v4 is starting and we will publish a blog post on > > the > > > > > roadmap and timeline for Camel v4 later this week. > > > > > > > > > > Some time next week we would like to switch "main" branch to v4, > and > > > then > > > > > create a new camel-3.x branch as the active branch for future Camel > > v3 > > > > > releases (next will be 3.21). > > > > > > > > > > The v4 is work in progress and in the beginning there will be > plenty > > of > > > > > stuff that fail tests, and components disabled as they have not yet > > > been > > > > > migrated to jakarta spec etc. So when we have the main branch > > switched > > > > then > > > > > more people can help with this work - where we can work on a per > > > > component > > > > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > > > > > > > > > > > > > -- > > > > > Claus Ibsen > > > > > - > > > > > @davsclaus > > > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > > > > > > > > > > > > >
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Hi The main branch is now v4 and this means you must use Java 17 to compile the code. On Wed, Jan 11, 2023 at 11:06 AM Guillaume Nodet wrote: > I pushed the changes. > > Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a > écrit : > > > Hi > > > > Guillaume is ready for pushing v4 to main branch. So he is doing this > now. > > Until he is done then please do not commit directly to main, but only do > > PRs > > > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > > wrote: > > > > > Branches have been created. > > > > > > CI jobs should updated. > > > > > > I guess we need to aling the regen action for 3.x, by pointing to the > new > > > branches. > > > > > > If something is missing, please report. > > > > > > Thanks > > > > > > -- > > > Andrea Cosentino > > > -- > > > Apache Camel PMC Chair > > > Apache Karaf Committer > > > Apache Servicemix PMC Member > > > Email: ancosen1...@yahoo.com > > > Twitter: @oscerd2 > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > > > wrote: > > > > > > > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > > > Once they are, we could create the branches. > > > > > > -- > > > Andrea Cosentino > > > -- > > > Apache Camel PMC Chair > > > Apache Karaf Committer > > > Apache Servicemix PMC Member > > > Email: ancosen1...@yahoo.com > > > Twitter: @oscerd2 > > > Github: oscerd > > > > > > > > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > > > > > > > Hi > > > > > > Lets try to get ready this week for switching main to v4. > > > Guillaume is back from PTO and will prepare his work today so it can be > > > ready for the switch. > > > In the meantime we need to prepare for the switch. > > > > > > We need to setup branches for v3 as its "main" branch. > > > - camel-3.x > > > - camel-spring-boot-3.x > > > - camel-karaf-3.x > > > > > > And have ASF CI servers able to build and test these branches (as it > does > > > today via main branch). > > > This allows Camel v3 to continue as is, as we need to keep maintaining > it > > > till the end of 2023. > > > > > > When we have these branches, then we need to remember to backport > commits > > > to these branches as well, > > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that > > > backporting commits is now potentially more branches: > > > > > > main > > > camel-3.x > > > camel-3.20.x > > > camel-3.18.x > > > camel-3.14.x > > > > > > It may be that before making the switch then Guillaume needs the "main" > > > branch to not have new commits for a couple of hours. > > > If so then lets us know Guillaume, as we can in the mean time then send > > > only work as PRs and then apply these after the switch. > > > > > > However when you are getting closer to make the switch then give us a > > heads > > > up here in this mail thread, thanks. > > > > > > > > > > > > > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen > > wrote: > > > > > > > Hi > > > > > > > > The work on Camel v4 is starting and we will publish a blog post on > the > > > > roadmap and timeline for Camel v4 later this week. > > > > > > > > Some time next week we would like to switch "main" branch to v4, and > > then > > > > create a new camel-3.x branch as the active branch for future Camel > v3 > > > > releases (next will be 3.21). > > > > > > > > The v4 is work in progress and in the beginning there will be plenty > of > > > > stuff that fail tests, and components disabled as they have not yet > > been > > > > migrated to jakarta spec etc. So when we have the main branch > switched > > > then > > > > more people can help with this work - where we can work on a per > > > component > > > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > > > > > > > > > -- > > > > Claus Ibsen > > > > - > > > > @davsclaus > > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > > > > > > > > -- > > > Claus Ibsen > > > - > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > -- > > Guillaume Nodet > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
I pushed the changes. Le mer. 11 janv. 2023 à 10:54, Claus Ibsen a écrit : > Hi > > Guillaume is ready for pushing v4 to main branch. So he is doing this now. > Until he is done then please do not commit directly to main, but only do > PRs > > On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino > wrote: > > > Branches have been created. > > > > CI jobs should updated. > > > > I guess we need to aling the regen action for 3.x, by pointing to the new > > branches. > > > > If something is missing, please report. > > > > Thanks > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > > wrote: > > > > > > > > > > > > There are some pending PRs waiting to be merged. > > > > Once they are, we could create the branches. > > > > -- > > Andrea Cosentino > > -- > > Apache Camel PMC Chair > > Apache Karaf Committer > > Apache Servicemix PMC Member > > Email: ancosen1...@yahoo.com > > Twitter: @oscerd2 > > Github: oscerd > > > > > > > > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > > claus.ib...@gmail.com> wrote: > > > > > > > > > > > > Hi > > > > Lets try to get ready this week for switching main to v4. > > Guillaume is back from PTO and will prepare his work today so it can be > > ready for the switch. > > In the meantime we need to prepare for the switch. > > > > We need to setup branches for v3 as its "main" branch. > > - camel-3.x > > - camel-spring-boot-3.x > > - camel-karaf-3.x > > > > And have ASF CI servers able to build and test these branches (as it does > > today via main branch). > > This allows Camel v3 to continue as is, as we need to keep maintaining it > > till the end of 2023. > > > > When we have these branches, then we need to remember to backport commits > > to these branches as well, > > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that > > backporting commits is now potentially more branches: > > > > main > > camel-3.x > > camel-3.20.x > > camel-3.18.x > > camel-3.14.x > > > > It may be that before making the switch then Guillaume needs the "main" > > branch to not have new commits for a couple of hours. > > If so then lets us know Guillaume, as we can in the mean time then send > > only work as PRs and then apply these after the switch. > > > > However when you are getting closer to make the switch then give us a > heads > > up here in this mail thread, thanks. > > > > > > > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen > wrote: > > > > > Hi > > > > > > The work on Camel v4 is starting and we will publish a blog post on the > > > roadmap and timeline for Camel v4 later this week. > > > > > > Some time next week we would like to switch "main" branch to v4, and > then > > > create a new camel-3.x branch as the active branch for future Camel v3 > > > releases (next will be 3.21). > > > > > > The v4 is work in progress and in the beginning there will be plenty of > > > stuff that fail tests, and components disabled as they have not yet > been > > > migrated to jakarta spec etc. So when we have the main branch switched > > then > > > more people can help with this work - where we can work on a per > > component > > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > > > > > -- > > > Claus Ibsen > > > - > > > @davsclaus > > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Guillaume Nodet
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Hi Guillaume is ready for pushing v4 to main branch. So he is doing this now. Until he is done then please do not commit directly to main, but only do PRs On Wed, Jan 11, 2023 at 9:57 AM Andrea Cosentino wrote: > Branches have been created. > > CI jobs should updated. > > I guess we need to aling the regen action for 3.x, by pointing to the new > branches. > > If something is missing, please report. > > Thanks > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino > wrote: > > > > > > There are some pending PRs waiting to be merged. > > Once they are, we could create the branches. > > -- > Andrea Cosentino > -- > Apache Camel PMC Chair > Apache Karaf Committer > Apache Servicemix PMC Member > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > > > > On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen < > claus.ib...@gmail.com> wrote: > > > > > > Hi > > Lets try to get ready this week for switching main to v4. > Guillaume is back from PTO and will prepare his work today so it can be > ready for the switch. > In the meantime we need to prepare for the switch. > > We need to setup branches for v3 as its "main" branch. > - camel-3.x > - camel-spring-boot-3.x > - camel-karaf-3.x > > And have ASF CI servers able to build and test these branches (as it does > today via main branch). > This allows Camel v3 to continue as is, as we need to keep maintaining it > till the end of 2023. > > When we have these branches, then we need to remember to backport commits > to these branches as well, > that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that > backporting commits is now potentially more branches: > > main > camel-3.x > camel-3.20.x > camel-3.18.x > camel-3.14.x > > It may be that before making the switch then Guillaume needs the "main" > branch to not have new commits for a couple of hours. > If so then lets us know Guillaume, as we can in the mean time then send > only work as PRs and then apply these after the switch. > > However when you are getting closer to make the switch then give us a heads > up here in this mail thread, thanks. > > > > > > On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen wrote: > > > Hi > > > > The work on Camel v4 is starting and we will publish a blog post on the > > roadmap and timeline for Camel v4 later this week. > > > > Some time next week we would like to switch "main" branch to v4, and then > > create a new camel-3.x branch as the active branch for future Camel v3 > > releases (next will be 3.21). > > > > The v4 is work in progress and in the beginning there will be plenty of > > stuff that fail tests, and components disabled as they have not yet been > > migrated to jakarta spec etc. So when we have the main branch switched > then > > more people can help with this work - where we can work on a per > component > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Branches have been created. CI jobs should updated. I guess we need to aling the regen action for 3.x, by pointing to the new branches. If something is missing, please report. Thanks -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, January 10, 2023 at 11:25:54 AM GMT+1, Andrea Cosentino wrote: There are some pending PRs waiting to be merged. Once they are, we could create the branches. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen wrote: Hi Lets try to get ready this week for switching main to v4. Guillaume is back from PTO and will prepare his work today so it can be ready for the switch. In the meantime we need to prepare for the switch. We need to setup branches for v3 as its "main" branch. - camel-3.x - camel-spring-boot-3.x - camel-karaf-3.x And have ASF CI servers able to build and test these branches (as it does today via main branch). This allows Camel v3 to continue as is, as we need to keep maintaining it till the end of 2023. When we have these branches, then we need to remember to backport commits to these branches as well, that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that backporting commits is now potentially more branches: main camel-3.x camel-3.20.x camel-3.18.x camel-3.14.x It may be that before making the switch then Guillaume needs the "main" branch to not have new commits for a couple of hours. If so then lets us know Guillaume, as we can in the mean time then send only work as PRs and then apply these after the switch. However when you are getting closer to make the switch then give us a heads up here in this mail thread, thanks. On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen wrote: > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
There are some pending PRs waiting to be merged. Once they are, we could create the branches. -- Andrea Cosentino -- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Tuesday, January 10, 2023 at 10:42:57 AM GMT+1, Claus Ibsen wrote: Hi Lets try to get ready this week for switching main to v4. Guillaume is back from PTO and will prepare his work today so it can be ready for the switch. In the meantime we need to prepare for the switch. We need to setup branches for v3 as its "main" branch. - camel-3.x - camel-spring-boot-3.x - camel-karaf-3.x And have ASF CI servers able to build and test these branches (as it does today via main branch). This allows Camel v3 to continue as is, as we need to keep maintaining it till the end of 2023. When we have these branches, then we need to remember to backport commits to these branches as well, that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that backporting commits is now potentially more branches: main camel-3.x camel-3.20.x camel-3.18.x camel-3.14.x It may be that before making the switch then Guillaume needs the "main" branch to not have new commits for a couple of hours. If so then lets us know Guillaume, as we can in the mean time then send only work as PRs and then apply these after the switch. However when you are getting closer to make the switch then give us a heads up here in this mail thread, thanks. On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen wrote: > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Hi Lets try to get ready this week for switching main to v4. Guillaume is back from PTO and will prepare his work today so it can be ready for the switch. In the meantime we need to prepare for the switch. We need to setup branches for v3 as its "main" branch. - camel-3.x - camel-spring-boot-3.x - camel-karaf-3.x And have ASF CI servers able to build and test these branches (as it does today via main branch). This allows Camel v3 to continue as is, as we need to keep maintaining it till the end of 2023. When we have these branches, then we need to remember to backport commits to these branches as well, that need to go into v3 for 3.21.0 and 3.22.0 releases. This means that backporting commits is now potentially more branches: main camel-3.x camel-3.20.x camel-3.18.x camel-3.14.x It may be that before making the switch then Guillaume needs the "main" branch to not have new commits for a couple of hours. If so then lets us know Guillaume, as we can in the mean time then send only work as PRs and then apply these after the switch. However when you are getting closer to make the switch then give us a heads up here in this mail thread, thanks. On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen wrote: > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
+1 It sounds good to me. Regards JB On Tue, Jan 3, 2023 at 11:46 AM Claus Ibsen wrote: > > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Sounds like a great plan and the blog post is very good :+1 On Tue, Jan 3, 2023 at 6:16 PM Karen Lease wrote: > +1 > Looking forward to helping with the upgrade! > > Le 03/01/2023 à 11:46, Claus Ibsen a écrit : > > Hi > > > > The work on Camel v4 is starting and we will publish a blog post on the > > roadmap and timeline for Camel v4 later this week. > > > > Some time next week we would like to switch "main" branch to v4, and then > > create a new camel-3.x branch as the active branch for future Camel v3 > > releases (next will be 3.21). > > > > The v4 is work in progress and in the beginning there will be plenty of > > stuff that fail tests, and components disabled as they have not yet been > > migrated to jakarta spec etc. So when we have the main branch switched > then > > more people can help with this work - where we can work on a per > component > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > >
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
+1 Looking forward to helping with the upgrade! Le 03/01/2023 à 11:46, Claus Ibsen a écrit : Hi The work on Camel v4 is starting and we will publish a blog post on the roadmap and timeline for Camel v4 later this week. Some time next week we would like to switch "main" branch to v4, and then create a new camel-3.x branch as the active branch for future Camel v3 releases (next will be 3.21). The v4 is work in progress and in the beginning there will be plenty of stuff that fail tests, and components disabled as they have not yet been migrated to jakarta spec etc. So when we have the main branch switched then more people can help with this work - where we can work on a per component style to fix tests, upgrade dependencies, and whatnot.
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
+1 On Tue, Jan 3, 2023 at 12:08 PM Zheng Feng wrote: > +1 > > On Tue, Jan 3, 2023 at 6:54 PM Claus Ibsen wrote: > > > Hi > > > > The work on Camel v4 is starting and we will publish a blog post on the > > roadmap and timeline for Camel v4 later this week. > > > > Some time next week we would like to switch "main" branch to v4, and then > > create a new camel-3.x branch as the active branch for future Camel v3 > > releases (next will be 3.21). > > > > The v4 is work in progress and in the beginning there will be plenty of > > stuff that fail tests, and components disabled as they have not yet been > > migrated to jakarta spec etc. So when we have the main branch switched > then > > more people can help with this work - where we can work on a per > component > > style to fix tests, upgrade dependencies, and whatnot. > > > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > -- Otavio R. Piske http://orpiske.net
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
+1 On Tue, Jan 3, 2023 at 6:54 PM Claus Ibsen wrote: > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
+1 Le mar. 3 janv. 2023 à 11:46, Claus Ibsen a écrit : > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Zineb
Re: [HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
+1. Exciting time is coming! Il mar 3 gen 2023, 11:46 Claus Ibsen ha scritto: > Hi > > The work on Camel v4 is starting and we will publish a blog post on the > roadmap and timeline for Camel v4 later this week. > > Some time next week we would like to switch "main" branch to v4, and then > create a new camel-3.x branch as the active branch for future Camel v3 > releases (next will be 3.21). > > The v4 is work in progress and in the beginning there will be plenty of > stuff that fail tests, and components disabled as they have not yet been > migrated to jakarta spec etc. So when we have the main branch switched then > more people can help with this work - where we can work on a per component > style to fix tests, upgrade dependencies, and whatnot. > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
[HEADS UP] - Switching main branch to Camel v4 (week 2 in 2023)
Hi The work on Camel v4 is starting and we will publish a blog post on the roadmap and timeline for Camel v4 later this week. Some time next week we would like to switch "main" branch to v4, and then create a new camel-3.x branch as the active branch for future Camel v3 releases (next will be 3.21). The v4 is work in progress and in the beginning there will be plenty of stuff that fail tests, and components disabled as they have not yet been migrated to jakarta spec etc. So when we have the main branch switched then more people can help with this work - where we can work on a per component style to fix tests, upgrade dependencies, and whatnot. -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
