Release Plan Mifos 2.1.3
Before Release
Team Owner |
Indiv Owner |
Task |
Due Date |
Status |
|---|---|---|---|---|
Eng |
VMH |
Add build/deploy of release branch on continuous integration server |
|
done |
QA |
LC |
Mark all issues in 2.1.3 as verified, begin functional testing of Initial Testing Candidate build |
5/30 |
|
Eng |
VMH |
Double-check licenses of any 3rd party libraries added since last release |
|
done |
Eng |
VMH/ AM |
Update release-upgrades.txt so correct db schema version name appears on sysinfo page- http://mifosforge.jira.com/browse/MIFOS-5034 |
5/27 |
|
PM |
VMH |
Revisit/define default configuration to ship with product (local.properties) |
|
done |
PM |
KC |
Update Configuration guide if needed |
|
done |
Eng |
VMH |
Update Developer Documentation (any changes in dev environment, etc), Update Past Releases page |
5/31 |
need to update Past Releases |
PM |
KC |
Update and Complete Release Notes, Upgrade Instructions |
5/30 |
|
Eng |
VMH |
Final Release Candidate build ready - no changes allowed after this date |
5/27 |
|
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 |
5/31 |
|
QA |
LC |
Testing of Release Candidate Complete, give go-ahead (do diff w/ previous release) |
5/31 |
|
QA |
LC |
Confirm all translations are in package and mifos runs in FR, SP, CN |
5/31 |
|
PM |
KC |
Final Documentation ready (release notes, etc) |
5/31 |
|
PM |
KC |
Mark versions in Jira as released |
6/1 |
|
QA |
LC |
Test Download, release notes pre-release page |
|
|
Eng |
|
Release Day: see below |
5/31 |
|
QA |
LC |
Report Test results and risks |
|
|
Release Day
Team Owner |
Indiv Owner |
Task |
Status |
|---|---|---|---|
Eng |
VMH |
Upload Release Binary Zip |
|
QA |
LC |
Test Live Download |
|
All |
EC |
Update download package on mifos.org |
|
PM/Eng |
KC |
Announce Release on functional, developer, and user lists |
|
PM/Eng |
VMH |
Announce Release on Sourceforge, Update Past Releases page |
|
Biz |
JM |
Announce Release internally at GF |
|
All |
|
Main:Launch Party |
|
After Release
Owner |
Task |
Due Date |
Status |
|---|---|---|---|
Biz |
info on Mifos.org |
|
|
QA |
update demo server |
3/9 |
|
EC |
update User Manual |
|
|
All |
Post Mortem |
|
|
AM |
tag release |
|
|
JJ |
Notify customers of new release, including any updates to upgrade |
3/9 |
|
Plan for rolling out release plan:
1) Get entire team's input on plan
2) Work with team leads (Biz, QA, Eng, PM) to assign specific owners to each task
3) Send out final release plan to all team members
4) Begin twice weekly check-in meetings for release which include bVMH triage decisions