In Quarkus 3 platform or as external extension?

[maxandersen]

in #337 (comment) its discussed having hazelcast be ready for inclusion in Quarkus 3 platform - I would like to make sure that is the right thing or maybe it makes more sense hazelcast becomes an external extension similar to i.e. neo4j is it or all the other quarkiverse projects.

Being in the platform should only be done if those maintaining hazelcast-client is able to participate and follow the regular updates in Quarkus platform. We've automated a lot of this but we know things can get busy and one might not be ready for inclusion all the time.

hazelcast was early member of Quarkus platform since at the time we didn't have the notion of external extensions which is now fully supported in CLi and code.quarkus.io. We now have that and it would be good to consider what makes the most sense for hazelcast?

@ldziedziul are you or someone else able to commit to check for regular updates in Quarkus platform or would it make more sense to be an external extension?