docs: document rkt release cycle #2741
Conversation
|
Do you want to add the post-release issues triaging as well? |
Documentation/devel/release.md
Outdated
|
|
||
| This section describes the typical release cycle of rkt: | ||
|
|
||
| 1. A [milestone](https://github.com/coreos/rkt/milestones) is created on GitHub, fixing the target date for a future release (typically every 2/3 weeks). |
There was a problem hiding this comment.
1. A GitHub [milestone](https://github.com/coreos/rkt/milestones) sets the target date for a future rkt release. Releases occur approximately every two to three weeks.
|
@alban: I think in @jonboulle plan, triaging neglected stuff is another task that can be performed during freeze day, I'll add it there. @joshix: thanks for the much needed proofreading! |
|
that was your suggestion, not mine, but I think it's a good one On 3 June 2016 at 08:56, Luca Bruno [email protected] wrote:
|
This tries to document current release model, tentatively introducing a buffer day to stabilize the release and better plan next ones.
7848c3c to
fc47534
Compare
|
Reworded according to @joshix notes and added an explicit mention of triaging. |
|
LGTM |
This tries to document current release model, tentatively
introducing a buffer day to stabilize the release and better
plan next ones.