On Thu, Nov 11, 2021 at 2:45 PM Zoran Regvart <[email protected]> wrote: > > Hi Cameleers, > > On Thu, Nov 11, 2021 at 2:38 PM David Jencks <[email protected]> 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 >
-1 agree with Andrea we want @dev to be human only emails so it's easy to follow topics there. In the past we had automated emails and it spammed this list. You can use another mailing list such as issues or we can create a new one for such purpose. > zoran > -- > Zoran Regvart -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
