ADR to consider adding feature mature in the documentation

[enekofb]

This PR raises an ADR to determine if we should provide guidance on the user documentation about feature maturity and if so, how to express that in a way that is effective without side-effects.

Currently in draft as it is just to present the problem statement, and a few potential actions for further input from prod-engineering.

[squaremo]

Are experimental (or otherwise not production-ready) features flagged as such in the user interface itself?

[enekofb]

Are experimental (or otherwise not production-ready) features flagged as such in the user interface itself?

No, we don't have maturity showing in the UI either. It is definitely in the same context but potentially provides info to end users. Documentation could be end users or admins like customer-side platform engineers or CRE.

[enekofb]

From @lizwarner-weave

• Check with comercial team
• Either "alpha / stable" to be a feature flag

[enekofb]

From @bigkevmcd

• Security not something that could measured in maturity is a yes o no -> security posture is

From @squaremo

• +1 on both previous
• we should include it in the UI too

[enekofb]

From @serboctor

• framing not from the stability but from the early access and the request for input

[enekofb]

Summary

• happy to explore that better expectations approach but to check with commercial team on the best approach for users and sales.

Jeff - @chawklit

[enekofb]

From @chawklit

• to have product updates in blogposts
• alpha / beta / stable seems adequate for the purpose. dont think will disincentive trying (but for example alpha might not in prod)
• to follow up with @joe-terrible @darrylweaver to get their input