Define criteria for different API maturity levels / API conventions

[pmorie]

In many places we refer to "alpha", "beta", and "stable" or "GA" API levels, but these are not formalized anywhere. We should explicitly define the properties of these different levels and criteria that must be met to be considered a particular level.

Closely related to the concept of API maturity levels is having clear API conventions that must be followed so that APIs within the ecosystem "feel" consistent and meet user expectations; we should also clearly define conventions for our APIs.

[aliok]

Is this still relevant?

[dprotaso]

We have the following document - can @knative/technical-oversight-committee review and see if it is sufficient https://github.com/knative/community/blob/main/mechanics/MATURITY-LEVELS.md

[psschwei]

The focus of the Maturity Levels doc is mostly about the process of migrating to core.

We've also got this page in the docs, though it's a Serving page, so Eventing / Functions might not follow these exactly. But if we had a common understanding, maybe we could pull some of the info on alpha / beta / GA from there into the Maturity Levels doc?

[dprotaso]

Talked during TOC Meeting - @psschwei will update the doc to incorporate the definitions of Alpha, Beta, GA.