About sending email about ci build of website failures on dev ML, I would use a different address, because in the past we had complains about too much emails or too much traffic from users. -- Andrea Cosentino ---------------------------------- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
On Thursday, November 11, 2021, 02:45:48 PM GMT+1, Zoran Regvart <zo...@regvart.com> wrote: Hi Cameleers, On Thu, Nov 11, 2021 at 2:38 PM David Jencks <david.a.jen...@gmail.com> wrote: > -The best way to show how the idempotency feature works, in > camel-kafka-connector, it's through an example. We'll use the [AWS2-S3 Source > connector](/camel-kafka-connector/next/reference/connectors/camel-aws2-s3-kafka-source-connector.html) > +The best way to show how the idempotency feature works, in > camel-kafka-connector, it's through an example. We'll use the [AWS2-S3 Source > connector](/camel-kafka-connector/0.11.0/reference/connectors/camel-aws2-s3-kafka-source-connector.html) Yeah, we need to reference concrete versions, there is no guarantee that a page will be present in the future. Though there is also no guarantee that it will be present from a concrete version once we stop building that version. Not sure what a good option would be here. > On a more general note, can we make jenkins website build failures email the > dev list? I have too hard a time detecting these problems. It seems that I > get plenty of emails from GH actions about other build failures, surely the > website is as important. +1 I can have a look at this zoran -- Zoran Regvart
