Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance the design proposal template with a graduation-criteria section #286

Open
EdDev opened this issue Apr 18, 2024 · 5 comments
Open

Comments

@EdDev
Copy link
Member

EdDev commented Apr 18, 2024

The current design proposal template [1] is missing graduation criteria and feature lifecycle section.
While suggesting an enhancement or change, it would be useful to put focus on the planning in regards to the feature graduation.

The subject has been discussed as part of the feature lifecycle proposal [2] and its relevance to the proposal template has been raised in this [3] thread.

[1] https://github.com/kubevirt/community/blob/main/design-proposals/proposal-template.md
[3] #251
[3] https://github.com/kubevirt/community/pull/251/files#r1489624264

Describe the solution you'd like:

It is suggested to update the design template with a new graduation criteria section that ref the feature-lifecycle and provides a plan for graduation.

Describe alternatives you've considered:
N/A

@iholder101
Copy link
Contributor

Thank you
/cc

@fabiand
Copy link
Member

fabiand commented Apr 19, 2024

@EdDev please see #288

As part of that proposal I'm suggesting to have an dedicated repo, with an issue per feature, and this issue is tracking the feature state until graduation. I'm suggesting a metadata file to track the graduation and deprecation more fine grained.

@kubevirt-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 18, 2024
@kubevirt-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 17, 2024
@iholder101
Copy link
Contributor

/remove-lifecycle rotten

@kubevirt-bot kubevirt-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants