| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
|
|
Signed-off-by: Max Xu <xuhuan@live.cn>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Deleted Old release-cycle.png
|
|
Updated tldr links in accordance to new Timeline
|
|
Changed Relase cycles timeline in accordance with new release cadence change. Changed release from four times a year to three times a year and changed the phases-: Normal Dev from to Weeks 1-11, Code freeze to Weeks 12-14 and Post release to Weeks 14+.
|
|
|
|
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
|
|
|
|
* hub -> gh
fall of from https://github.com/kubernetes/kubernetes/pull/97697
* Also permissions are changed with the tool switch
gh auth login requires way more permissions
* Update cherry-picks.md
|
|
Signed-off-by: Stephen Augustus <foo@auggie.dev>
|
|
Update the kubernetes-versions guide to avoid referencing `gsutil` and
URI's that have GCS bucket names hardcoded in them where possible.
We don't have a CLI accessible way to list the contents of a given build
through dl.k8s.io, so it was necessary to keep it there.
Anything else that uses http or https to download kubernetes artifacts
should always use dl.k8s.io. It greatly reduces the amount of code that
will need to change whenever a different location is used (GCS bucket
rename, some other backing store, etc.)
|
|
* docs: clarify github tokens and cherry-pick script
* emphasize interactive instructions
* Update contributors/devel/sig-release/cherry-picks.md
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
Co-authored-by: Sergey Kanzhelev <S.Kanzhelev@live.com>
|
|
|
|
Fixes code block formatting in guide for flake finders episode 000.
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
|
|
|
|
Updates cherry pick guide to note that applicable patches must be made
to all active release branches at the same time so that the fix will be
included for each in the same round of patch releases.
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
|
|
Updates flake finders episode 0 README.md with host links.
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
|
|
Adds show notes for the first episode of flake finder fridays.
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
|
|
Adds a dedicated area for flake finder fridays show assets under
sig-release developer documentation.
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
|
|
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
|
|
As of the KEP
https://git.k8s.io/enhancements/keps/sig-release/1498-kubernetes-yearly-support-period
becoming implementable for 1.19, we should note this change in the
developer guide description of the release process and lifecycle.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
|
|
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
|
|
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
|
|
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
|
|
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
|
|
The file is no longer being published by ci-kubernetes-e2e-gci-gce
|
|
|
|
Add more milestone info to the release doc
|
|
|
|
|
|
cherry-picks: bump up guidance on criteria, add table of contents
|
|
We see a relatively high volume of cherry picks that aren't clearly
meeting the criteria for cherry-picking, but that criteria has only
recently started to be in written, shared form and it is not super
discoverable. To make it more clear let's make that its own section
(linkable), move it earlier in the document, and add a table of contents
to the cherry-picks.md for navigation.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
|
|
There has been a fair amount of ambiguity, even deliberately, around
what is a valid candidate for backporting to a stable release branch of
Kubernetes. For some the criteria is simply "critical bug fixes", but
this is also something that lacks definition. This documentation update
attempts to better describe what is expected of and what can be expected
by somebody proposing a cherry-pick on one of our stable release branches.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
|
|
|
|
We're adding a GitHub team for the patch managers and have a group mail
alias to make it easier contacting the folks who shepherd cherry picks
across the arc of time, documented in the release repo.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
Cherry picks are now mostly handled primarily through automation,
including their release note block. In some cases that release
note automation may fail (multiple candidate release notes from
which to pick) and human intervention is required, but this amounts
to just adding the otherwise normal `release-note` block in the
pull request description.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
|
|
|
|
|
|
updated
|
|
|
