Update the feature stage to our definition
Open
Nobody has claimed this yet.
kind/documentation
- Dominant language
- SCSS
- Stars
- 19
- Forks
- 117
- Avg merge
- 13h 29m
- Merged PRs (30d)
- 13
Description
In some cases we still us Experimental
https://docs.kubermatic.com/kubermatic/v2.27/architecture/supported-providers/baremetal/
Let's align them to the definition
https://docs.kubermatic.com/kubermatic/v2.27/architecture/feature-stages/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the supported providers bare-metal page and compare its feature-stage labels with the linked feature-stages definition. Update each remaining Experimental designation to match that definition, then review the page to confirm all referenced stages are consistent.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100