As we move our team to "No Feature Freeze" (No-FF) delivery, we need to make a few changes to our downstream repository (full context can be found here: No-FF Presentation).

To move a downstream repo to no-FF:

1. Ensure that “QE/Docs/PX-approved” labels are added to the team’s repos
   1. Example: https://github.com/openshift/cloud-credential-operator/labels?q=qe-approved
   2. Example: https://github.com/openshift/aws-pod-identity-webhook/labels?q=docs-approved
2. Create a PR to enable the requirement of either “QE/Docs/PX-approved labels” or “Valid-Bug” (with the standard additional “lgtm” and “approved” labels)

1. 1. Example: https://github.com/openshift/release/pull/20282
   2. Cc Ben Parees on PR if reviewer is needed

1. Continue to work on stories/features & PR that the team plans to deliver 
2. (Important) reach out to your QE/Doc/PX team members for approval before feature merges
3. If bugs are discovered, it is encouraged to use Bugzilla Jira  to communicate issues 
4. Merge features before Code Freeze 
5. Conduct retrospective of the new process with team

(Taken from here)

A/C:

 - Points 1 and 2 of the list above are completed