Hi Kafka devs,

Lately we started using "early access", "production ready" and also
"preview" to determine the grade of "production readiness" of the features
we deliver to our community.
However, as far as I know, there is no official definition from the Apache
Kafka side on which are the graduation steps for features and what type of
"guarantees" each of these offer.

I think we should agree on which terms we should use and what each of these
exactly mean in terms of reliability. So far it seems we have this
graduation steps:
- Early Access: Feature is just complete but not yet fully polished and
maybe not used in production in many environments
- Preview: Feature was early access before and it underwent at least a
cycle of improvements and fixes and it's used in some production
environments maybe
- Production ready: Feature is officially released and it fulfills the
expected initial needs

Note that we don't offer any guarantees or SLA/SLO in the classical term.

Is this something we can agree on? What do those terms mean to you? Do we
need more steps? Or do we need less steps?

Best,
-- 
[image: Aiven] <https://www.aiven.io>

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io <https://www.aiven.io>   |   <https://www.facebook.com/aivencloud>
  <https://www.linkedin.com/company/aiven/>   <https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa, Hannu Valtonen,
Anna Richardson, Kenneth Chen
Amtsgericht Charlottenburg, HRB 209739 B

Reply via email to