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

Epic: Improve feature versioning #6966

Closed
12 of 13 tasks
JeromeJu opened this issue Jul 24, 2023 · 6 comments
Closed
12 of 13 tasks

Epic: Improve feature versioning #6966

JeromeJu opened this issue Jul 24, 2023 · 6 comments
Labels
area/epic Issues that should be considered as Epics (aka multiple sub-tasks, …) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@JeromeJu
Copy link
Member

JeromeJu commented Jul 24, 2023

This epic tracks the subtasks on improving Tekton pipeline feature versioning including feature flag improvements, documentations, maintenance routine and cleanups etc.

🎏 Feature flag improvements

📑 Documentations

  • Update our policies/development guide/TEP process to mention that new features start out in the alpha track
  • Update our policies to mention that new feature authors should open an issue to track the feedback on that feature and promotion to beta once the feature lands in a release
  • Better documentations for feature stability levels

📝 Maintenance routine

  • Consider retroactively opening issues to track feedback/promotion for current features in alpha
  • Implement a quarterly alpha feature review to come up to review current features in alpha (this does not preclude moving features to beta outside of this review. This is mostly a way to ensure all alpha features are reviewed on a regular basis). First one schedule for September 12 during the API WG.

🧹 Cleanup

@tekton-robot
Copy link
Collaborator

@JeromeJu: The label(s) kind/epic cannot be applied, because the repository doesn't have them.

In response to this:

/kind epic

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot
Copy link
Collaborator

@JeromeJu: The label(s) kind/epic cannot be applied, because the repository doesn't have them.

In response to this:

/kind Epic

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@vdemeester
Copy link
Member

/area epic

@tekton-robot tekton-robot added the area/epic Issues that should be considered as Epics (aka multiple sub-tasks, …) label Jul 25, 2023
@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 23, 2023
@vdemeester
Copy link
Member

/lifecycle frozen

@tekton-robot tekton-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 23, 2023
@JeromeJu
Copy link
Member Author

JeromeJu commented Feb 13, 2024

Closing with the completion of the following: #5632, #6592 and #6948

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/epic Issues that should be considered as Epics (aka multiple sub-tasks, …) lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

3 participants