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

Add internal schedule for release notes PRs #2499

Merged
merged 5 commits into from
Jun 6, 2024
Merged

Add internal schedule for release notes PRs #2499

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0486a38
add internal schedule for release notes PRs
npolshakova May 10, 2024
6a2935d
pr feedback
npolshakova May 20, 2024
69a3ba1
add release notes reviewer
npolshakova May 24, 2024
f0c8048
remove commented out sections
npolshakova May 24, 2024
eb26758
move schedule out of handbook, into v1.31 release
npolshakova Jun 5, 2024
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
14 changes: 14 additions & 0 deletions release-team/role-handbooks/release-notes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,20 @@ A "Dependencies" section should be curated which outlines how external dependenc

## Release Cycle Milestone Activities:

### Week 0

Create a table to track `Release`, `Branch Created Day`, `Week of Release`, `PR Merge Deadline`, `Release Notes Assignee`
and `Release Notes Reviewer` based on the release timeline. This will serve as an internal schedule and signup sheet for
the release notes team to follow. The schedule is used to track progress and give status updates during release team meetings.

##### Release Team Meeting Updates

For the release team meeting, provide a `status` based on the following criteria:
- A `Red` on our release notes status means that we are delayed past the deadline or there is a major blocker for our work to create Release Notes pull requests.
- A `Yellow` status generally means that we are still within the deadline of creating the Release Notes pull request, but
there are things (minor blockages, `krel` issues, etc.) that could cause a delay past the PR merge deadline.
- A `Green` status means that everything looks good and done from Release Notes team side, i.e. the release notes pull requests are being created, reviewed and merged before the deadline. Everything is A-OK here.

### Week 1

Begin running release-notes tool for the ongoing collection of release notes with the first alpha release, which has been cut directly after the latest minor.
Expand Down
15 changes: 15 additions & 0 deletions releases/release-1.31/release-notes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
### Release Notes Milestones

This is the internal schedule for the Release Notes team to follow for creating Release Notes PRs. This is based on the
[v1.31 release](https://github.com/kubernetes/sig-release/tree/master/releases/release-1.31) timeline.

| **Release** | **Week** | **Branch Created Day** | **PR merge deadline** |
|------------------------------------|----------|-------------------------|--------------------------|
| 1.31.0-alpha.1 released | week 4 | Tuesday 4th June 2024 | Tuesday 11th June 2024 |
| 1.31.0-alpha.2 released | week 6 | Tuesday 18th June 2024 | Tuesday 25th June 2024 |
| 1.31.0-alpha.3 released | week 8 | Tuesday 2nd July 2024 | Tuesday 13th July 2024 |
| 1.31.0-beta.0 released | week 10 | Tuesday 16th July 2024 | Tuesday 23rd July 2024 |
| Start final draft of Release Notes | week 11 | Tuesday 23rd July 2024 | Tuesday 13th August 2024 |
| 1.31.0-rc.0 released | week 12 | Tuesday 30th July 2024 | Tuesday 6th August 2024 |
| 1.31.0-rc.1 released | week 13 | Tuesday 6th August 2024 | Tuesday 13th August 2024 |