Mifos 2.2.3 Release Plan

Release Plan Mifos 2.2.3

Before Release

Team Owner

Indiv Owner

Task

Due Date

Status

PM

LC

Set up Release Plan team meeting(s)

01/03

(tick)

Eng

JS

Communicate code freeze to developer list (template), and release schedule to community

01/03

(tick)

Eng

JS

Create release branch in source control

-

(tick)

Eng

JS

Add build/deploy of release branch on continuous integration server

-

(tick)

QA

LC

Begin functional testing of Initial Testing Candidate build

01/04

(tick)

All

JS

Scrub bug list during general bug triage meeting; fixing only show-stoppers after this point

01/04

(tick)

Eng

JS

Bump artifact versions in Maven POMs to next release. Rev module versions on head/master and plugins/master

-

(tick)

Eng

JS

Double-check licenses of any 3rd party libraries added since last release

-

(tick)

Eng

JS

Update release-upgrades.txt so correct db schema version name appears on sysinfo page.  Tag release with appropriate version number.

-

(tick)

PM

JS

Revisit release packaging - Documentation (if any new or removed docs, actual content revisited later)

01/04

(tick)

PM

JS

Revisit/define default configuration to ship with product (local.properties)

01/04

(tick)

Eng

JS

Update Install File bundled in zip (INSTALL in top level of source control)

01/04

(tick)

PM

JS

Update Configuration guide, Update custom properties that ships with Mifos with new additions

01/04

(tick)

Eng

JS

Update System Recommendations, Client Machine Recommendations

01/04

(tick)

Eng

JS

Update Developer Documentation (any changes in dev environment, etc)

01/04

(tick)

PM

JS

Update and Complete Release Notes, Upgrade Instructions (note changes in hardware/software and specific versions to upgrade to, also special upgrade procedures)

01/04

(tick)

PM

JS

Update Functional Specs (UpdateinFS bugs, any new or updated features)

01/04

(tick)

Eng

JS

Final Release Candidate build ready - no changes allowed after this date

01/04

(tick)

Eng

JS

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

01/04

(tick)

QA

LC

Confirm all translations are in package and mifos runs in FR, SP, CN

01/04

(tick)

QA

LC

Testing of Release Candidate Complete, give go-ahead (do diff w/ previous release)

01/04

(tick)

Biz

EC

Create Draft announcement for mifos.org

01/04


PM

EC

Create Draft announcement for community

01/04


Biz

EC

Create Draft announcement for customers

01/04


PM

JS

Final Documentation ready (release notes, install doc, etc)

01/04

(tick)

PM

JS

Mark versions in Jira as released

01/04

(tick)

QA

LC

Test Download, release notes pre-release page

01/04

(tick)

Biz

EC

Update links on mifos.org (download page, download form - 2 links, and homepage block)

01/04


Eng

 

Release Day: see below

01/04

 

QA

LC

Report Test results and risks

01/04

(tick)

Release Day

Team Owner

Indiv Owner

Task

Status

Eng

JS

Upload Release Binary Zip

(tick)

QA

LC

Test Live Download


All

EC

Announce Release on mifos.org


PM/Eng

EC

Announce Release on functional, developer, and user lists


Biz

EC

Announce on Social Media


PM/Eng

EC

Announce Release on Sourceforge

 

Biz

EC

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


 

EC

update User Manual

 

 

All

Post Mortem

 

 

JS

tag release

01/04

(tick)

JJ

Notify customers of new release, including any updates to upgrade


 

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 bug triage decisions