Add Milestone Release Issue template

Now that releases will be done upon request, it makes sense to be able to easily create corresponding release issues on demand.

.github/ISSUE_TEMPLATE/Bug.md

@@ -1,6 +1,10 @@
 ---
 name: Bug report
 about: Report a bug with odo
+title: ''
+labels: ''
+assignees: ''
+
 ---
 
 /kind bug
@@ -34,5 +38,3 @@ Thanks for understanding, and for contributing to the project!
 
 
 ## Any logs, error output, etc?
-
-

.github/ISSUE_TEMPLATE/Documentation.md

@@ -1,6 +1,10 @@
 ---
 name: Documentation
 about: Report mistakes or request for documentation
+title: ''
+labels: ''
+assignees: ''
+
 ---
 
 /area documentation
@@ -26,5 +30,3 @@ Thanks for understanding, and for contributing to the project!
 
 
 ## What is the relevance of it?
-
-

.github/ISSUE_TEMPLATE/Feature.md

@@ -1,6 +1,10 @@
 ---
 name: Feature request
 about: Suggest a new feature for odo
+title: ''
+labels: ''
+assignees: ''
+
 ---
 
 /kind feature
@@ -22,4 +26,3 @@ Thanks for understanding, and for contributing to the project!
 
 
 ## Why is this needed?
-

.github/ISSUE_TEMPLATE/UserStory.md

@@ -1,6 +1,10 @@
 ---
 name: User Story
 about: New User Story
+title: ''
+labels: ''
+assignees: ''
+
 ---
 
 /kind user-story

.github/ISSUE_TEMPLATE/milestone-release.md

@@ -0,0 +1,26 @@
+---
+name: Milestone Release
+about: Create issue to release a new version of odo
+title: "\U0001F389 [VERSION] Milestone Release \U0001F389 "
+labels: area/release-eng, kind/task
+assignees: ''
+
+---
+
+/kind task
+/area release-eng
+
+Issue to track work for publishing a new release of `odo`:
+
+- Target release process start date: **[TBD]**
+- Errata date (when we expect the binaries to be published): **[TBD]**
+- Version: **[VERSION]**
+- OCP Version: **[TBD]**
+- Once the release is done, make sure the link to download `latest` points to this new version: https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/odo/latest/
+
+Notes:
+- Make sure this issue is linked to a corresponding milestone, which should contain all necessary issues and/or PRs.
+- A draft PR will be generated by the @github-actions bot when a new GitHub Release is created (it can be a pre-release). This PR will contain all the necessary changes (`build/VERSION`, blog post, release notes, ...).
+  - Feel free to review and adjust the content
+  - Merge this PR once the release binaries are available on the Content Gateway
+- ~The docs team wants to start testing a process for optional docs approval on advisories. A pilot will start in early July. Check if this release can leverage this process to validate it.~