Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
Kubernetes 1.10 - Left Shark.png
README.md
burndown_meeting_minutes_archive.md
exceptions.yaml
features.csv
release-1.10.md
release-notes-draft.md
release_team.md

README.md

Kubernetes 1.10 Release Schedule

Handy Links:

tl;dr The 1.10 release cycle begins on Tuesday, January 2nd, 2018, and ends on release day, Wednesday, March 21st. Feature freeze is Monday, January 22nd. Code freeze begins Monday February 26th and ends Wednesday, March 14th. Docs must be completed and reviewed by Friday, March 9th.

Notes About this Release

  • The feature process is remaining as it has in prior releases.
  • Features that don't have complete code and tests by Code Freeze may be disabled by the release team before cutting the first beta.
  • The release team will escalate release-master-blocking failures to SIGs throughout the cycle, not just near release cuts.
  • Key deliverables (e.g. initial release cuts) tend to be scheduled on Tuesdays to maintain context while ramping up and then responding to any problems. The final release will be on a Wednesday in keeping with prior practice.
  • The release length is nearly 12 weeks
  • Code name "Left Shark" because it's been my favorite meme of the release cycle (Thanks Christoph)

Timeline

What Who JAN FEB MAR APR DEV WEEK TEST GATES
Start of Release Cycle Lead 2 week 1
Finalize Schedule Lead 5
Begin collecting planned work from SIGs Lead, Features Lead 8 week 2
Begin weekly release team meetings Lead 9
Begin weekly status reports at Community Lead, Shadow 11
Finalize Release Team Lead 12
Start Release Notes Draft Release Notes Lead 15 week 3
Clean up features repo Features Lead 15
1.10.0-alpha.2 release Branch Manager 16 master-blocking
"Feature Freeze" begins (EOD PST) Feature Lead 22 week 4
1.10.0-alpha.3 release Branch Manager 30 week 5 master-blocking
Blog post: what we're working on for 1.10 Communications 6 week 6
1.10.0-beta.0 release Branch Manager 13 week 7 master-blocking, master-upgrade
Create 'release-1.10' branch and begin daily branchff Branch Manager 13
All release branch CI jobs created Test Infra Lead 16
Begin Code Slush Bot, Lead 20 week 8
Begin code freeze (EOD PST) Bot, Lead 26 week 9 1.10-blocking, master-blocking, master-upgrade
Begin MWF Burndown meetings Lead 26
Begin pruning Lead and release team 26
1.10.0-beta.1 release Branch Manager 27 1.10-blocking, master-blocking, master-upgrade
Docs deadline - PRs ready for review Docs Lead 2
1.10.0-beta.2 release Branch Manager 6 week 10 1.10-blocking, master-blocking, master-upgrade
Docs complete - All PRs reviewed and ready to merge Docs Lead 9
Begin M-F Burndown meetings Lead 12 week 11
End of code freeze (EOD PST) Bot, Lead 19 week 12
Perform final branchff Branch Manager 19
1.10.0-rc.1 release Branch Manager 19 1.10-blocking, master-blocking, master-upgrade
Master branch re-opens for 1.11 Bot, Branch Manager 19
PRs for v1.10.0 must be cherry picked to release-1.10 Branch Manager 19
Notify kubernetes-dev of lifting code freeze Lead 20
v1.10.0 Branch Manager 26 week 13 1.10-blocking
v1.11.0-alpha.1 Branch Manager 27
Release retrospective Community 29
1.11 Release Cycle Begins Next Lead 2

Details

Feature Freeze

All features going into the release must have an associated issue in the features repo by Monday, January 22nd. That issue must be in the 1.10 milestone. SIG "themes" should also be in the release notes draft at this time to prepare for blog posts and release marketing. Any work the SIG wants publicized needs to be called out to the Features Lead so the Release Team communications lead can work with SIG-PM and the CNCF.

Code Slush

Starting on Tuesday, February 20th, only PRs labeled by their owner SIGs with status/approved-for-milestonewill be allowed to merge into the master branch. All others will be deferred until the end of Code Freeze, when master opens back up for the next release cycle. If necessary, the release team can add the status/approved-for-milestone label in cases where the SIG approvers do not have permissions to do so.

Code Slush begins prior to Code Freeze to help reduce noise from miscellaneous changes that aren't related to issues that SIGs have approved for the milestone. Feature work is still allowed at this point, but it must follow the process to get approved for the milestone. SIGs are the gatekeepers of this label, not the release team.

Exceptions

Starting at Code Slush, the release team will solicit and rule on exception requests for feature and test work that is unlikely to be done by Code Freeze. As with the status/approved-for-milestone label, the exception approval is the responsibility of the SIG or SIGs labeled in the pull request. The release team may intervene or deny the request only if it poses a risk to release quality, or could negatively impact the overall timeline. Changes introduced at this point should be well-tested, well-understood, limited in architectural scope, and low risk. All of those factors should be considered in the approval process.

Code Freeze

All features going into the release must be code-complete (including tests) and have docs PRs open by Monday, February 26th.

The docs PRs don't have to be ready to merge, but it should be clear what the topic will be and who is responsible for writing it. This person will become the primary contact for the documentation lead. It’s incredibly important that documentation work gets completed as quickly as possible.

After this point, only release-blocking issues and PRs will be allowed in the milestone. The milestone bot will remove anything that lacks the priority/critical-urgent label, as well as other required labels.

Pruning

Features that are partially implemented and/or lack sufficient tests may be considered for pruning beginning after code freeze, unless they've been granted exceptions.

The release team will work with SIGs and feature owners to evaluate each case, but for example, pruning could include actions such as:

  • Disabling the use of a new API or field
  • Switching the default value of a flag or field
  • Moving a new API or field behind an Alpha feature gate
  • Reverting commits or deleting code

This needs to occur before 1.10.0-beta.1 is cut so we have time to gather signal on whether the system is stable in this state. These are considered drastic measures, so the release team will strive to coordinate at-risk work with SIGs before this time. The goal is to make code freeze, and overall project transparency, enforceable despite the lack of a feature branch process.

Docs

If a feature needs documentation, enter Yes in the feature tracking spreadsheet and add a link to the documentation PR. You can open documentation PRs in the kubernetes/website repository. If you have questions, the release documentation lead, or representatives from SIG-Docs will be happy to assist you.

For documentation PRs:

  • Open PRs against the release-1.10 branch based off of the 1.10 release PR. The documentation workflow uses feature branches for release documentation, rather than basing from master. Be sure to open your PR against the release branch.
  • Add your PR to the 1.10 Release milestone.

Burndown

Burndown meetings are held on Mondays, Wednesdays and Fridays at 10AM Pacific until the final release is near, and then every business day until the release. On Thursdays of the final 2 weeks, the meeting will happen alongside the Community Meeting.

Join the Kubernetes Milestone Burndown Group to get the calendar invite.

The intent of these meetings is to:

  • Focus on fixing bugs, eliminating test flakes and general release stabilization.
  • Ensure docs and release notes are written and accurate.
  • Identify all features going into the release, and make sure alpha, beta, ga is marked in features repo.
  • Provide a one-stop view of release progress including relevant release metrics.
  • Host SIG stakeholders for updates.