Hi Josep, I think it’s high time that this was tackled. I suggest that it would be best handled as a KIP because then we have a document which can be discussed and improved, followed by a formal vote.
A standard set of terms with agreed meanings would be very helpful for some of the larger KIPs which take many releases to be properly ready for prime time. Most KIPs don’t need this, but a handful definitely do. Personally, I like the sequence that KIP-848 has taken, moving from Early Access, to Preview, and finally complete. I intend to follow the same sequence for KIP-932. Thanks, Andrew > On 31 Jul 2024, at 10:15, Josep Prat <josep.p...@aiven.io.INVALID> wrote: > > Also as part of this discussion I would like to flag that we need to be > able to know how we can flag this properly so it's known for the Release > Manager. > For example, a KIP is approved, the Jira associated with it is being worked > on. Release happens, Jira is still open, how can we flag that this KIP is > in early access, or preview? > > Best, > > On Wed, Jul 31, 2024 at 11:03 AM Josep Prat <josep.p...@aiven.io> wrote: > >> 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 >> > > > -- > [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
