ensure components in distributions match guidelines

[codeboten]

There are several components in the contrib distribution that are still marked as development in the contrib repository. It would be great if there was a check that validated that components included in the distribution have a stability level of at least Alpha to match the expectation set by the distribution guideline

[codeboten]

Here's the list of components as of 03-Jul-2024

[mowies]

What would you expect would be the consequence of the suggested check? Blocking the release? Just a warning? Creating an issue in the contrib repo?

[jpkrohling]

For the components that are already part of a released version of contrib, they should be changed to be alpha (which is what @codeboten showed in the screenshot), as that's what they effectively are (at least). For new components, the PR shouldn't be merged until the component is at least alpha.

[codeboten]

What would you expect would be the consequence of the suggested check? Blocking the release? Just a warning? Creating an issue in the contrib repo?

Ideally, a check could run on each PR to the manifests, to validate that the components match the guidelines. As a starting point, checking that all components are marked alpha for the contrib distro would have caught this issue

[mowies]

I guess it should be enough to check that the development key doesn't exist in the metadata.yml file for each component?

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.