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

Create a release checklist for a more formal release process #541

Open
microwavables opened this issue Sep 2, 2022 · 1 comment
Open
Assignees
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@microwavables
Copy link
Contributor

Describe the problem/challenge you have
Currently there is no set process for major releases for the team to follow for a more consistent experience. This creates chaos when trying to plan for communications, content, and promotion of the releases.

Describe the solution you'd like
I would like to create a release checklist for the team to follow for upcoming major releases.

Anything else you would like to add
This checklist will only be for more major releases/new feature releases and not minor, i.e. bug fixes.

@microwavables microwavables added the carvel triage This issue has not yet been reviewed for validity label Sep 2, 2022
@microwavables microwavables self-assigned this Sep 2, 2022
@aaronshurley aaronshurley added enhancement This issue is a feature request carvel accepted This issue should be considered for future work and that the triage process has been completed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed carvel triage This issue has not yet been reviewed for validity labels Sep 13, 2022
@neil-hickey
Copy link
Contributor

hey @microwavables !

I happened to be creating a release checklist for secretgen-controller and kapp-controller, and just noticed this issue. Here's some links to the new issue templates, let me know / feel free to make a PR to edit these as you see fit if they don't align with what you were expecting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed enhancement This issue is a feature request priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

3 participants