Planning for Fineract 1.5 Release

[Ed Cable <ed...@mifos.org>]

Hello community,

This email kicks off the planning process for the next release, Fineract
1.5

If you have any features you've built or bug fixes you'd like to contribute
please discuss that on the list prior to November 27.

By November 27, we want to announce the plans for the release with
everything that's planning to be included at 80% code-complete. Anything
that's not ready by then should be targeted for the 1.6 release.

Please create a corresponding ticket on JIRA and tag with 1.5.0 if that
issue doesn't already exist. Make sure you link to your pull request from
the issue on JIRA.

Please discuss on this thread, add to this wiki page or open and tag
tickets with the release fix version of 1.5.0

Release Page on Wiki:
https://cwiki.apache.org/confluence/display/FINERACT/1.5.0+-+Apache+Fineract
JIRA Filter for Issues Tagged 1.5.0:
https://issues.apache.org/jira/issues/?filter=12347544

We welcome volunteers and partners to pick up any of the critical bugs
tagged for 1.5.0 that still need to be fixed - it's a great way to build
merit!



Plans for Release Apache Fineract 1.5

Planning Release - Nov 13

Announce Release - Nov 27

QA - Nov 27 - Dec 11

Publish Release Notes - Dec 11

Vote on Release - Dec 18

Target release date - Dec 25

Stage

Description

Proposed Length

How Far in Advance of Release (Proposed)

How Far in Advance of Release (Currently)

Planning of Next Release

Discuss with community what would like to ship in next release and what
people could work on.

Create fix version on JIRA to assign to.

Action: modify existing email template to open up planning process,
schedule a meeting to discuss and set a tentative branching date (i.e. 2
weeks later, if release date is a month past that).

.

1 week

6 weeks

Doesn’t Exist

Announcement of Release

Announce what is going to come in the release (should be 80% done at least).

Cut a release branch and freeze release branch and then develop branch can
still have active work on it but only in rare cases might anything
additional from develop

Email out sharing release branch details

4 weeks prior

1 - 2 months

QA

QA begins on the release branch - staging Server setup

Might fix some regression issues

1 - 2 weeks

4 weeks prior

JIRA Sanitization/Publish RElease Notes

Sanitize release documentation

Create release notes and email community release information with links.


2 weeks prior

Vote

Create artifacts, sign release, etc. Open up votes

1 week prior

Release

Tally up votes, announce, update websites and infrastructure with new
release artifacts.

Release date