Added release criteria to release-instructions (#3598)

Signed-off-by: Dave Smith-Uchida <dsmithuchida@vmware.com>

site/content/docs/main/release-instructions.md

@@ -14,6 +14,32 @@ This page covers the steps to perform when releasing a new version of Velero.
 - Pre-releases: Any release leading up to a GA. Example: 1.4.0-beta.1, 1.5.0-rc.1
 - RC releases: Release Candidate, contains everything that is supposed to ship with the GA release. This is still a pre-release.
 
+## Velero Release Requirements
+
+Velero is on a "train leaves the station" model for releases.  We will generate a release candidate (RC)
+at the scheduled time.  Multiple release candidates may be generated, depending on if bugs are found during testing.
+When testing has passed a release build will be generated.
+
+### Release Candidate criteria
+The release candidate commit must meet the following criteria:
+
+* No major bugs outstanding 
+* Unit tests pass
+* E2E tests against latest Kubernetes on AWS, vSphere and kind pass
+
+Once the release has moved to RC, a code freeze is in effect.  Only changes needed to release are allowable.
+
+### Release criteria
+In order for a release candidate to be released, it must meet the following criteria:
+
+* Unit tests pass
+* E2E tests against latest K8S and earliest supported K8S on Azure, vSphere, Kind, AWS, GCP
+* Manual tests pass (manual tests will be converted to automated testing)
+
+When bugs are identified by any of these methods, we will determine whether the bug is a release blocker or not and
+a fix generated if it is.  When release blocker bugs identifies in an release candidate are fixed, another RC will
+be generated and the test cycle will restart.
+
 ## Preparing
 
 ### Create release blog post (GA only)