Why is this important?
At our face-to-face, Engineering determined the "definition of done" for the new Quay MVP UI as the following before deploying the UI publicly on Quay.io.
Additionally other ** requirements integral to our launch in the UI is API configuration to enable scalability and implementing a UX Analytic tool to track user activity before and after our launch.
These requirements ensure baseline parity with the current Quay.io UI that will enable user to have the most essential functionality required before demoing the beta version of the product.
The first launch on quay.io will be without sign up page flow and will require users old login information
- Robot tokens
- Teams and Membership
- Default Permissions