NOTE: This page slightly overlaps with the more technically detailed How to Release Apache Fineract step-by-step documentation.
We aim to release monthly releases on a time-driven release cycle based on the following phases to plan and manage each release. Soon we'll have a scrum boards up on JIRA to track the stories in each release and manage the backlog for future releases.
Stage | Description | Proposed Length | How Far In Advance of Target Release Date |
---|---|---|---|
Planning of Next Release | Discuss with community the features that are ready to be integrated and we would like to ship in the next release. Management of the backlog to plan out what features and tasks are available to work on will be coordinated separately. Tasks:
. | 1 - 2 weeks | 6 weeks |
Announcement of Release | Announce what is going to come in the release (should be 80% done at least). Tasks:
| 4 weeks | |
QA | QA begins on the release branch
| 1 - 2 weeks | 4 weeks |
JIRA Sanitization & Publish Release Notes | Sanitize release documentation Tasks:
| 2 weeks | |
Vote | Publicly vote for release amongst community with binding votes from committers Tasks
| 1 week | |
Release | Tally up votes, announce, update websites and infrastructure with new release artifacts. | Release Date |
...