Open elnyry-sam-k opened 8 months ago
Hey team! Please add your planning poker estimate with Zenhub @JaneS321 @TW-Ei-Nghon-Phoo @bushjames @kyaw-soe-tw @SithuKyaw-Thitsaworks @zinzinnyohlaing-tw @karimjindani @PaulMakinMojaloop
Hello @elnyry-sam-k , for the tech doc tasked, we have also a big epic. Can we please ensure that the twos are completely independent?
@elnyry-sam-k , can we have a clear list of acceptance criteria for this epic? For example, what does that mean to have the branch protected? and are the key steps for CI documented? Thanks a lot :)
Thanks for reviewing @JulieG19.
The four items listed are the acceptance criteria.
On the specific questions: 1) Branch protection rules are applied on primary (main currently) branches to protect against direct commits and other similar operations. 2) The key CI steps are listed in the first point.
As a Mojaloop adopter I want all existing Mojaloop code quality and security pipeline steps to be executed against vNext repositories so that I can have the same level of confidence in a vNext based release, or any new feature implemented on the vNext codebase.
Acceptance criteria:
This epic captures several DevOps and quality related issues (not exhaustive) to be implemented to support an RC based on vnext codebase. This includes:
Mojaloop vnext repos (listed below) need to have CI/CD steps similar to current Mojaloop codebase which involve:
The readme pages of the documentation need to contain basic sections from the template used that consists of details to the basic description, testing, coverage, and CI/CD (Continuous Integration/Continuous Deployment) process for the following BC
Beta "release" on GitHub with features covered and deployment instructions to be provided at service/BC level and bundled as a single "beta" release
Main branches protected on GitHub repos with key CI steps passing on merges.
Repo list:
Separate Epics for functional issues, bugs, settlement related, FSPIOP have been created.