From 4a5f25ea3e7c1a94ac9e36b7d68dd19999d0af85 Mon Sep 17 00:00:00 2001
From: Tim Pepper <tpepper@vmware.com>
Date: Mon, 8 Oct 2018 11:35:15 -0700
Subject: [PATCH] release docs: clarify tldr table html

I incorrectly had indicated a milestone was required in each of the four
major phases of the release cycle, where it is not in the "normal dev"
phase.  Not sure how we got that through review.  Part of it may have
been the html table format.  To help with that, in addition to removing
the errant indication of milestone as required in that early period,
I've also added html comments in the table so the reader of the raw code
can more clearly see which section is which.

Signed-off-by: Tim Pepper <tpepper@vmware.com>
---
 contributors/devel/release.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/contributors/devel/release.md b/contributors/devel/release.md
index 6d0dcbefd..31270f731 100644
--- a/contributors/devel/release.md
+++ b/contributors/devel/release.md
@@ -56,7 +56,7 @@ If you want your PR to get merged, it needs the following required labels and mi
 <td>Required Labels</td>
 <td>
 <ul>
-<li>/milestone {v1.y}</li>
+<!--Weeks 1-8-->
 <li>/sig {name}</li>
 <li>/kind {type}</li>
 <li>/lgtm</li>
@@ -65,6 +65,7 @@ If you want your PR to get merged, it needs the following required labels and mi
 </td>
 <td>
 <ul>
+<!--Week 9-->
 <li>/milestone {v1.y}</li>
 <li>/sig {name}</li>
 <li>/kind {type}</li>
@@ -75,6 +76,7 @@ If you want your PR to get merged, it needs the following required labels and mi
 </td>
 <td>
 <ul>
+<!--Weeks 10-12-->
 <li>/milestone {v1.y}</li>
 <li>/sig {name}</li>
 <li>/kind {bug, failing-test}</li>
@@ -85,6 +87,7 @@ If you want your PR to get merged, it needs the following required labels and mi
 </td>
 <td>
 <ul>
+<!--Weeks 12+-->
 <li>/milestone {v1.y}</li>
 <li>/sig {name}</li>
 <li>/kind {bug, failing-test}</li>