Document requirements for components moving stability levels and reaching 1.0

[mx-psi]

We have a list of component stability levels, as well as guidelines for configuration changes. We also have the concept of a component being 1.0.

Based on some recent discussions on the Collector SIG (2024-10-23) and the Collector stability working group (2024-10-28), it would beneficial to have a consolidated document with a list of requirements for a component to move through the stability stages and for reaching 1.0

• Move existing stability level definitions to a document in the docs/ folder #11560
• Move configuration changes guidelines to the new document #11571
• Document observability requirements for stable components #11581
• Document relation between signal stability levels and component versioning #11851
• Establish codeowners minimum criteria for moving up through the stability ladder #11850
• Document documentation requirements for stable components #11852
• Document testing and coverage requirements for stable components #11867
• Document resiliency requirements for stable components #11866
• Document scalability requirements for stable components #11593
• Document performance testing requirements for stable components #11868
• Document SemConv compatibility requirements for components stability #11878

[mx-psi]

For resiliency, we may want to consider a requirement about persistent storage support (at least under graceful termination situations)

[mx-psi]

We may also want to have requirements about keeping the size of internal state in check for stateful components