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

docs: Add release process info for maintainers #336

Merged
merged 1 commit into from Jul 8, 2022

Conversation

znewman01
Copy link
Contributor

Signed-off-by: Zachary Newman z@znewman.net

Please fill in the fields below to submit a pull request. The more information that is provided, the better.

Fixes #335
Release Notes: N/A

This proposes a "cut a patch version at any time, but give everyone a 24hr heads-up in case there are objections" policy. I think this is fine because we maintain a green HEAD at all times, but I'm open to other suggestions (though preference is to keep the process lightweight for patch versions).

CC all maintainers since this affects process: @rdimitrov @asraa @joshuagl @mnm678 @trishankatdatadog @ethan-lowman-dd @hosseinsia

mnm678
mnm678 previously approved these changes Jul 6, 2022
Signed-off-by: Zachary Newman <z@znewman.net>
@znewman01
Copy link
Contributor Author

I'll give it another day and then merge, unless I see objections :)

CI failure seems to be related to coverage data upload, so probably a flake. May have to investigate if we see this more often.

@znewman01 znewman01 merged commit 0f17236 into theupdateframework:master Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document release instructions
3 participants