Additional feedback: 1. For "Preview", I don't think it has to be complete or api stable and it's definitely not ready for production. My take is that "preview" is close on all of those: roughly speaking no apis changes are planned, the system is robustly tested and the functionality is mostly there. But we reserve the right to change APIs if necessary (this is the last chance) and so on.
Ismael On Fri, Nov 8, 2024 at 1:32 PM Ismael Juma <m...@ismaeljuma.com> wrote: > Hi all, > > I am coming late to this discussion, but I am a bit confused. We seem to > talk about levels 1 to 4 (which I think are very opaque and unusual) and at > some point we have names: "In Development", "Experimental", "Preview" and > "Production Ready". What are we actually proposing? If the latter, let's > have those names instead of levels everywhere. If the former, then I don't > think it works. > > Ismael > > On Wed, Nov 6, 2024 at 2:27 AM Josep Prat <josep.p...@aiven.io.invalid> > 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 >> >
