Hi Josep, Continuing the discussion from the other thread: I'm still not 100% convinced that we need a distinction between "in development" and "experimental." In both cases, end-users can't make use of the feature. So why not condense them into one step?
With regard to "preview", I think "use in production: maybe" doesn't give very clear guidance. Is it better to just say no or "not recommended"? Or someone otherwise indicate that preview is mostly about testing the feature. best, Colin On Wed, Nov 6, 2024, at 02:27, Josep Prat wrote: > Hi all, > The discussion about graduation steps for KIPs has now stabilized and I'd > like to start a vote for it. Here you can find the KIP: > https://cwiki.apache.org/confluence/x/mYn9Eg > > Thanks, > -- > [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
