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.

Sign up for GitHub

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

Jump to bottom

Propose pre-release (RC) as part of our process #1315

Merged
merged 4 commits into from
Sep 3, 2020
Merged

Propose pre-release (RC) as part of our process #1315

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
128c530
Propose pre-release (RC) as part of our process
alenkacz Jan 28, 2020
f2f64e6
Added notes which changes to include in the release nots for pre-prel…
ANeumann82 Sep 3, 2020
d0843c4
Merge branch 'main' into av/propose-prerelease
ANeumann82 Sep 3, 2020
04c98b3
Changed "2 days before" to "at least 2 days before"
ANeumann82 Sep 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ The KUDO Project is aiming to do monthly minor releases but the period could be
1. RM is responsible for following the process below
1. RM should announce the release in the public [#kudo slack channel](https://kubernetes.slack.com/messages/kudo/) at least two days prior to the date
1. RM makes sure all PRs that need to go into the release are merged prior to the process starting
1. RM prepares a pre-release 2 days before the release process is started and makes sure it's manually tested at least in the parts where we lack automatic tests for now (pre-release should be announced in the [#kudo slack channel](https://kubernetes.slack.com/messages/kudo/))

### Release Process

Expand Down