...
Team Owner | Indiv Owner | Task | Due Date | Status |
|---|---|---|---|---|
PM | KC | Set up Release Plan team meeting(s) | 6/16 |
|
Eng | KC | Communicate code freeze to developer list (template), and release schedule to community | 6/17 |
|
Eng | VMH | Create release branch in source control |
| DONE |
Eng | VMH | Add build/deploy of release branch on continuous integration server |
| DONE |
QA | LC | Begin functional testing of Initial Testing Candidate build | 6/17 |
|
All | LC | Scrub bug list during general bug triage meeting; fixing only show-stoppers after this point |
|
|
Eng | VMH | Bump artifact versions in Maven POMs to next release. Rev module versions on head/master and plugins/master |
|
|
Eng | VMH | Double-check licenses of any 3rd party libraries added since last release |
|
|
Eng | VMH | Update release-upgrades.txt so correct db schema version name appears on sysinfo page |
|
|
PM | KC | Revisit release packaging - Documentation (if any new or removed docs, actual content revisited later) |
|
|
PM | VMH | Revisit/define default configuration to ship with product (local.properties) |
|
|
Eng | VMH | Update Install File bundled in zip (INSTALL in top level of source control. Update Upgrade instructions (note changes in hardware/software and specific versions to upgrade to, also special upgrade procedures) |
|
|
PM | KC | Update Configuration guide (MPESA), Update custom properties that ships with Mifos with new additions |
|
|
PM | KC | Demo release to Prof. Services |
|
|
Eng | VMH | Update System Recommendations, Client Machine Recommendations |
|
|
Eng | VMH | Update Developer Documentation (any changes in dev environment, etc) |
|
|
PM | KC | Update and Complete Release Notes, Upgrade Instructions |
|
|
PM | KC | Update Functional Specs (UpdateinFS bugs, any new or updated features) |
|
|
Eng | VMH | Final Release Candidate build ready - no changes allowed after this date |
|
|
Eng | VMH | Identify final release candidate (binary release Zip File with Installation Doc, War file, and supporting code). Note: binary release .zip files are automatically generated with every release branch build. Make sure language files are included |
|
|
QA | LC | Confirm all translations are in package and mifos runs in FR, SP, CN |
|
|
QA | LC | Testing of Release Candidate Complete, give go-ahead (do diff w/ previous release) |
|
|
Biz | EC | Create Draft announcement for mifos.org |
| |
PM | KC | Create Draft announcement for community |
| |
Biz | JJ | Create Draft announcement for customers |
|
|
PM | KC | Final Documentation ready (release notes, install doc, etc) |
| |
PM | KC | Mark versions in Jira as released |
|
|
QA | LC | Test Download, release notes pre-release page |
| |
Eng |
| Release Day: see below |
|
|
QA | LC | Report Test results and risks |
|
|
...