summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorguineveresaenger <guineveresaenger@github.com>2019-10-08 20:58:45 -0700
committerguineveresaenger <guineveresaenger@github.com>2019-10-10 10:38:00 -0700
commite195eff0d92c841e3be276129066c6fcc7d741d7 (patch)
treedebc811b1c4ea472b65dec081417c8976bb7e8b4
parentaf31c5f9751e49e313e9660b6fa37e9221ec07d5 (diff)
Add short definitions for release phases and link to release phase doc
-rw-r--r--contributors/devel/sig-release/release.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/contributors/devel/sig-release/release.md b/contributors/devel/sig-release/release.md
index 3cfa1624..11c9e7fc 100644
--- a/contributors/devel/sig-release/release.md
+++ b/contributors/devel/sig-release/release.md
@@ -107,7 +107,11 @@ be consistent across artifact types.
contact info for the team associated with any given release can be
found [here](https://git.k8s.io/sig-release/releases/).
- *Y days*: Refers to business days (using the location local to the release-manager M-F).
-- *feature*: see "[Is My Thing a Feature?](http://git.k8s.io/features/README.md#is-my-thing-a-feature)
+- *enhancement*: see "[Is My Thing an Enhancement?](https://git.k8s.io/enhancements/README.md#is-my-thing-an-enhancement)
+- *[Enhancement Freeze](https://git.k8s.io/sig-release/releases/release_phases.md#enhancements-freeze)*: Usually during Week 4 of a release cycle: the deadline by which KEPs have to be completed in order for enhancements to be part of the current release
+- *[Exception Request](https://git.k8s.io/sig-release/releases/release_phases.md#exceptions)*: The process of requesting an extension on the deadline for a particular Enhancement
+- *[Code Freeze](https://git.k8s.io/sig-release/releases/release_phases.md#code-freeze)*: The period of ~4 weeks before the final release date, during which only critical bug fixes are merged into the release.
+- *[Pruning](https://git.k8s.io/sig-release/releases/release_phases.md#pruning)*: The process of removing an Enhancement from a release milestone if it is not fully implemented or is otherwise considered not stable.
- *release milestone*: semantic version string or [GitHub milestone](https://help.github.com/articles/associating-milestones-with-issues-and-pull-requests/) referring to a release MAJOR.MINOR vX.Y version. See also [release versioning](http://git.k8s.io/community/contributors/design-proposals/release/versioning.md)
- *release branch*: Git branch "release-X.Y" created for the vX.Y milestone. Created at the time of the vX.Y-beta.0 release and maintained after the release for approximately 9 months with vX.Y.Z patch releases.