<aside> ๐ก This template is designed as a standalone document for individual projects. It is a living document, and new ideas and old ideas here should be evaluated iteratively.
</aside>
<aside> ๐ The release train doesnโt wait for anyone. On a biweekly schedule, there will be new features, tests, and deployments that will work together in unison. If you are not able to catch this deployment train, you better catch the next one!
</aside>
<aside> ๐ The purpose and goals of this document are to write down how DxGov handles its releases going forward. This document will provide a coordinated effort between the development team, QA team, product manager, and our stakeholders.
</aside>
<aside> โ โA successful release cycle means a fast build-to-deployment time with no unexpected bugsโ
</aside>
The following cycle represents an agile release management cycle, and we are going to proceed from the eight stages presented below:
Bugs and Features
Planning and Design
Software Build
Review
Test
Deployment
Support
Issue Reporting and collections
<aside> ๐ฅ The DxGov Team
</aside>
Name | Role |
---|---|
Kenny | Developer |
Madusha | Developer |
Milton | Developer |
Dino | Developer |
Augusto | Developer/Developer Manager |
Ross | Product Manager |
Tomas | Developer |
Philip | QA |