Re: Camel Quarkus 2.2.1 LTS in preparation

2022-01-13 Thread Claus Ibsen
We do not need any docs, its not for development its for users that can patch camel-quarkus in production On Thu, Jan 13, 2022 at 7:43 PM David Jencks wrote: > > What’s going to happen about docs? There are no 2.2.x docs at the moment…. I > assumed 2.2.x was obsolete and unsupported. Given

Re: Please check that any documentation changes build!!

2022-01-13 Thread Zoran Regvart
Hi Cameleers, I do think that it's not ideal to break the website build, but also I don't think it's avoidable. I don't think it's a big issue if the website fails to build -- I consider the build more as a gating check; and to that end we didn't publish a broken website for the community. And I

Re: Website build and CI error - overall improved a lot

2022-01-13 Thread Zoran Regvart
Hi Cameleers, On Thu, Jan 13, 2022 at 6:07 AM David Jencks wrote: > — you have to build the site locally to see the built page that shows the > problem. Maybe Zoran knows a way, but I don’t know how to see the CI built > site if the build broke. We could, both on Jenkins* and on GitHub

Re: Website build and CI error - overall improved a lot

2022-01-13 Thread Jeremy Ross
Indeed, very nice work, David. Thank you! On Wed, Jan 12, 2022 at 11:07 PM David Jencks wrote: > The spring-boot completeness check is a complicated thing…. Antora isn’t > really designed to run IT tests :-) > > Do you have any suggestions about how to make fixing such problems easier > or

Re: Camel Quarkus 2.2.1 LTS in preparation

2022-01-13 Thread David Jencks
What’s going to happen about docs? There are no 2.2.x docs at the moment…. I assumed 2.2.x was obsolete and unsupported. Given the length of time they have been missing, making them work will take some effort. David Jencks > On Jan 13, 2022, at 3:46 AM, Claus Ibsen wrote: > > On Thu, Jan

Re: Camel Quarkus 2.2.1 LTS in preparation

2022-01-13 Thread Claus Ibsen
On Thu, Jan 13, 2022 at 10:32 AM Peter Palaga wrote: > > Hi, > > this is a heads up that we are preparing the release of Camel Quarkus > 2.2.1 these days. > > The main motivation was to fix the recent Log4j vulnerabilities in the > Camel Quarkus branch based on Camel 3.14 LTS. Backporting those

Camel Quarkus 2.2.1 LTS in preparation

2022-01-13 Thread Peter Palaga
Hi, this is a heads up that we are preparing the release of Camel Quarkus 2.2.1 these days. The main motivation was to fix the recent Log4j vulnerabilities in the Camel Quarkus branch based on Camel 3.14 LTS. Backporting those fixes, we told ourselves to backport a bit more fixes to have a