kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Mention extension idea

pull/7321/head
Thomas Stromberg 2020-03-30 08:49:21 -07:00
parent 15ddaf723e
commit f1be224721
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
enhancements/proposed/20200316-release-schedule/schedule-proposal.md
View File

@ -54,3 +54,16 @@ Even with this schedule, it is assumed that release dates may slip.
### Release branches
Rather than considering master to always be in a releasable state, we could maintain long-lived release branches. This adds a lot of overhead to the release manager, as they have to manage cherry-picks.
### Extending cycle by a week
As this process assumes a regression release at Day 7, it begs the question on whether or not a 5-week feature release cycle makes more sense:
* Day 0: Create milestones for the next regression & feature release
* Day 7: Regression release (optional)
* Day 21: Beta release
* Day 28: Beta 2 release
* Day 31: Feature freeze and optional final beta
* Day 35: Feature release
The downside is a slightly lower release velocity, the upside may be more a more stable final release.