Oh if I understand correctly you idea:

- release ckc 0.11.0 based on camel 3.11 generating connectors the old way
- merge kamelets into main and generate connectors just from kamelets from 3.12 
onward

Is that what you have in mand? If yes you have my +1 :)

On Mon, Sep 20, 2021, at 09:12, Claus Ibsen wrote:
> Hi
> 
> Great to see progress on CKC.
> 
> Before doing the "kamelet" thingy. I wonder if we can get a 0.11.0
> release out that is just "the old way" but for the 3.11 LTS release.
> Then users have that stable Camel version to stay on.
> 
> Then the kamalet work can be merged after that and go into releases
> for Camel 3.12 onwards.
> 
> And yeah I agree that we should get to a point where its only
> generated from kamelets. Then that also ensures that users that more
> easily jump from CKC to Camel-K.
> We could also do a release without the old way as nobody needs all the
> 300 components in Camel. But then the CKC community can give feedback
> on connectors needed and we build kamelets for that.
> 
> If a old connector is needed we could ship the maven plugin so CKC
> users can generate a custom connector themseleves as "fallback"
> 
> On Sat, Sep 18, 2021 at 10:53 PM Andrea <[email protected]> wrote:
> >
> > Hello,
> >
> > finally the switch to use kamelets in Camel Kafka Connector project is in 
> > an usable state:
> >
> > https://github.com/apache/camel-kafka-connector/tree/kamelets
> >
> > this branch has refactored the existing core in reusable kamelets and has 
> > added generation of kafka connectors using the kamelet catalog as well. The 
> > generation happens using the following criteria:
> >
> > - one kafka connector is generated for each kamelet in the kamelet catalog.
> > - one kafka connector is generated for each camel component ("the old 
> > way"), excluding the component used in at least one kamelet.
> >
> > Going forward, as the kamelet catalog will add more kamelets, I personally 
> > prefer to further reduce the number of kafka connectors generated "the old 
> > way" (most probably selecting just the most meaningful/used/that makes 
> > sense).
> >
> > These would made the project more maintainable by reducing number of 
> > connectors and improving their quality by reusing kamelets that are the 
> > preferred way in camel to define "connectors" and are used/will be used 
> > across all runtimes.
> >
> > I would like to give everyone interested some time to look at the work and 
> > think about improvements/concerns before merging it to main and shortly 
> > after releasing a new version of Camel Kafka Connector.
> >
> > Regards,
> > Andrea.
> 
> 
> 
> -- 
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
> 

Reply via email to