Closed adutra closed 3 years ago
Hello @ppalaga, our plans so far were to wait until Quarkus 2.0.0.Final is out, then release the Cassandra extension 1.1.0. As we understand it, this would give us roughly a week for the Quarkus Platform to be updated with the newly-released Cassandra extension. Would that work for you? If not, I guess we could look into releasing against Quarkus 2.0.0.CR3.
our plans so far were to wait until Quarkus 2.0.0.Final is out, then release the Cassandra extension 1.1.0. As we understand it, this would give us roughly a week for the Quarkus Platform to be updated with the newly-released Cassandra extension. Would that work for you?
That worked pretty well so far, but this time I guess the risk of incompatibilities is a bit higher due to so many major upgrades in Quarkus and elsewhere. There is also the new Quarkus platform composition and config https://github.com/quarkusio/quarkus-platform/pull/232 that may or may not work well for you, for us (Camel Quarkus) and for you and us in combination :) All these things are much easier to test on CI with proper releases than with snapshots or similar. A CR release would be very appreciated.
We discussed this internally and we should get an RC release for you early next week.
Thanks! I see there is 1.1.0-rc1. Let me upgrade and test in Camel Quarkus.
We'd very much appreciate a cassandra-quarkus release based on Quarkus 2.0.0.CR3 to be able to test with Camel Quarkus and even on Quarkus Platform. Is there any hope for it?