Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Release Plan Mifos 2.1.6

Before Release

Team Owner

Indiv Owner

Task

Due Date

Status

PM

LC

Set up Release Plan team meeting(s)

9/12

(tick)

Eng

JS

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

-

(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

9/12

(tick)

All

JS

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

9/12

(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.

9/12

(tick)

PM

JS

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

-

(tick)

PM

JS

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

-

(tick)

Eng

JS

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)

-

(tick)

PM

JS

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

-

(tick)

Eng

JS

Update System Recommendations, Client Machine Recommendations

-

(tick)

Eng

JS

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

-

(tick)

PM

JS

Update and Complete Release Notes, Upgrade Instructions

-

(tick)

PM

JS

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

-

(tick)

Eng

JS

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

9/12

(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

9/12

(tick)

QA

LC

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

9/12

(tick)

QA

LC

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

9/12

(tick)

Biz

ET

Create Draft announcement for mifos.org

9/13


PM

ET

Create Draft announcement for community

9/13


Biz

ET

Create Draft announcement for customers

9/13


PM

JS

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

9/13

(tick)

PM

JS

Mark versions in Jira as released

9/13

(tick)

QA

LC

Test Download, release notes pre-release page

9/13

(tick)

Eng

 

Release Day: see below

9/13

 

QA

LC

Report Test results and risks

9/13

(tick)

Release Day

Team Owner

Indiv Owner

Task

Status

Eng

JS

Upload Release Binary Zip

(tick)

QA

LC

Test Live Download

(tick)

All

ET

Announce Release on mifos.org

 

PM/Eng

ET

Announce Release on functional, developer, and user lists

 

PM/Eng

ET

Announce Release on Sourceforge

 

Biz

ET

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

9/12

(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

  • No labels