Improve release process post v16.0.0 GA code freeze (vitessio#12487)

* Update the release instructions document with pre-requisites for release team Signed-off-by: Florent Poinsard <[email protected]> * Add Do Not Merge to release Pull Request upon creation Signed-off-by: Florent Poinsard <[email protected]> --------- Signed-off-by: Florent Poinsard <[email protected]>
planetscale · Mar 1, 2023 · 1119fd6 · 1119fd6
1 parent 752cd50
commit 1119fd6
Showing 1 changed file with 9 additions and 1 deletion.
diff --git a/doc/internal/ReleaseInstructions.md b/doc/internal/ReleaseInstructions.md
@@ -118,9 +118,17 @@ Create the `settings.xml` in the `$HOME/.m2/` directory as described in their [i
 
 ## Release Cutover 
 
-In this section we describe our current release process. We begin with a short [**overview**](#overview).
+In this section we describe our current release process. We begin with a list of [**pre-requisite for the release team**](#pre-requisites) and with a short [**overview**](#overview).
 The release process is divided into three parts: [**Pre-Release**](#pre-release), [**Release**](#release), [**Post-Release**](#post-release), which are detailed after the overview.
 
+### Pre-Requisites
+
+This section highlights the different pre-requisites the release team has to meet before releasing.
+
+- The tool `gh` must be installed locally and ready to be used.
+- You must have access to the Java release, more information in the [**Java Packages**](#java-packages) section.
+- You must be able to create branches and have admin right on the `vitessio/vitess` and `planetscale/vitess-operator` repositories.
+
 ### Overview
 
 #### Schedule