Merge pull request #6428 from kunalchhabra37/master

Updated the latest release cycle docs from 3 to 4 months

5 files changed, 10 insertions, 10 deletions

diff --git a/contributors/devel/sig-release/release-cycle.jpg b/contributors/devel/sig-release/release-cycle.jpg
new file mode 100644
index 00000000..8519fca6
--- /dev/null
+++ b/contributors/devel/sig-release/release-cycle.jpg
diff --git a/contributors/devel/sig-release/release-cycle.png b/contributors/devel/sig-release/release-cycle.png
deleted file mode 100644
index f3aa460a..00000000
--- a/contributors/devel/sig-release/release-cycle.png
+++ /dev/null
diff --git a/contributors/devel/sig-release/release-lifecycle.jpg b/contributors/devel/sig-release/release-lifecycle.jpg
new file mode 100644
index 00000000..ac30788b
--- /dev/null
+++ b/contributors/devel/sig-release/release-lifecycle.jpg
diff --git a/contributors/devel/sig-release/release-lifecycle.png b/contributors/devel/sig-release/release-lifecycle.png
deleted file mode 100644
index 090dabab..00000000
--- a/contributors/devel/sig-release/release-lifecycle.png
+++ /dev/null
diff --git a/contributors/devel/sig-release/release.md b/contributors/devel/sig-release/release.md
index f3cb608c..2b3495c9 100644
--- a/contributors/devel/sig-release/release.md
+++ b/contributors/devel/sig-release/release.md
@@ -5,9 +5,9 @@ create an enhancement, issue, or pull request which targets a specific release
 milestone.
 
 - [TL;DR](#tldr)
-  - [Normal Dev (Weeks 1-8)](#normal-dev-weeks-1-8)
-  - [Code Freeze (Weeks 9-11)](#code-freeze-weeks-9-11)
-  - [Post-Release (Weeks 11+)](#post-release-weeks-11)
+  - [Normal Dev (Weeks 1-11)](#normal-dev-weeks-1-11)
+  - [Code Freeze (Weeks 12-14)](#code-freeze-weeks-12-14)
+  - [Post-Release (Weeks 14+)](#post-release-weeks-14+)
 - [Definitions](#definitions)
 - [The Release Cycle](#the-release-cycle)
 - [Removal Of Items From The Milestone](#removal-of-items-from-the-milestone)
@@ -42,14 +42,14 @@ requirements exist when the target milestone is a prior release (see
 If you want your PR to get merged, it needs the following required labels and
 milestones, represented here by the Prow /commands it would take to add them:
 
-### Normal Dev (Weeks 1-8)
+### Normal Dev (Weeks 1-11)
 
 - /sig {name}
 - /kind {type}
 - /lgtm
 - /approved
 
-### [Code Freeze][code-freeze] (Weeks 9-11)
+### [Code Freeze][code-freeze] (Weeks 12-14)
 
 - /milestone {v1.y}
 - /sig {name}
@@ -57,7 +57,7 @@ milestones, represented here by the Prow /commands it would take to add them:
 - /lgtm
 - /approved
 
-### Post-Release (Weeks 11+)
+### Post-Release (Weeks 14+)
 
 Return to 'Normal Dev' phase requirements:
 
@@ -124,9 +124,9 @@ The general labeling process should be consistent across artifact types.
 
 ## The Release Cycle
 
-![Image of one Kubernetes release cycle](release-cycle.png)
+![Image of one Kubernetes release cycle](release-cycle.jpg)
 
-Kubernetes releases currently happen approximately four times per year.
+Kubernetes releases currently happen approximately three times per year.
 
 The release process can be thought of as having three main phases:
 
@@ -177,7 +177,7 @@ under that automation umbrella should be have a milestone applied.
 Implementation and bug fixing is ongoing across the cycle, but culminates in a
 code freeze period.
 
-**[Code Freeze][code-freeze]** starts in week ~10 and continues for ~2 weeks.
+**[Code Freeze][code-freeze]** starts in week ~12 and continues for ~2 weeks.
 Only critical bug fixes are accepted into the release codebase during this
 time.
 
@@ -192,7 +192,7 @@ back to the release branch. The release is built from the release branch.
 
 Each release is part of a broader Kubernetes lifecycle:
 
-![Image of Kubernetes release lifecycle spanning three releases](release-lifecycle.png)
+![Image of Kubernetes release lifecycle spanning three releases](release-lifecycle.jpg)
 
 ## Removal Of Items From The Milestone