...
Date | Version | Author | Approver/Reviewer | Comment |
Oct’23 | 1.0.0 | Idris Aliyu | Kevin N’geno | |
July’24 | 1.1.0 | Idris Aliyu | Updated Release Process to include monthly release cycles |
1.0 Responsibilities
1.1 Technical Product Manager Responsibilities:
...
See flow chart below for the QA process.
...
2.1.1 Release Cycle
DCIR is moving to a monthly release cycle to deliver regular updates to our banking partners.
Here's what you can expect:
Monthly Releases: New features and bug fixes will be rolled out on a monthly basis.
DCIR Suite Versioning: Each release will introduce a new DCIR Suite version number. This version will reflect the updated versions of all components included in the suite.
Benefits:
Faster Innovation: Monthly releases allow us to deliver new features and improvements more frequently.
Improved Stability: Regular updates help address bugs and potential issues proactively.
Simplified Tracking: Clear versioning simplifies tracking changes and managing deployments for banks.
Here's a breakdown of the steps involved in the new DCIR monthly release cycle:
Release Preparation
Jar Compilation: Updated JAR (Java Archive) files for all services included in the release will be compiled and stored within the designated product version folder on the DCIR Google Drive: https://drive.google.com/drive/folders/1lGUeegdrP6bNqIlvn5eIMWqO8jSW3VGB?usp=drive_link
Release Documentation
Release Notes: A detailed document outlining the features, enhancements, and bug fixes included in the release will be created and shared with the banks: https://docs.google.com/document/d/1VgdmxLSda5oTtxvNa6zfgCsTBlBw-q9Ym2OH1LufLbo/edit?usp=drive_link
Deployment Notes: Internal documentation detailing deployment steps, updated configuration files, component diagrams, and relevant application properties will be created. This will be shared with the tech support team and provided to banks on demand. https://docs.google.com/document/d/1e_4bS2nGhHz6KBj4nqPzR2rDJ7T-Fqi2U3cIpY0hEzw/edit?usp=sharing
Change Approval
Change Advisory Board (CAB) Review: All changes and product releases must be approved by the CAB. This approval will be granted following a successful demonstration and walkthrough of the intended changes by the Technical Product Manager (TPM), Quality Assurance (QA), or Enterprise Architect (EA) responsible for the release.
For increased transparency, the DCIR portal landing page will now prominently display the current DCIR Suite version.
2.2 Sprint Management Process
...