Improve Gitaly Cluster demo script and feature acceptance criteria
Problem
Praefect is rapidly adding new features and changes for Gitaly Cluster requirements. This is becoming harder to test and validate since the Gitaly team moves at their own speed and official QA is not required for closing issues.
While we perform a weekly demo to test new features, our script is not actively maintained by the entire team. During demos, we have trouble remembering what new features or fixes need evaluation.
Proposal
Require new features for Praefect to document setup, test steps, and acceptance criteria in the demo script. Version control the demo script so that the changes can be done at the same time as a new feature. Only close the issue and remove the relevant demo steps once the feature or fix passes acceptance criteria in the demo.