This document is currently under discussion

Release branches are created every two months at the beginning of the following month from the changes that were merged by the last day of the previous month.

If a feature is almost but not quite done at the end of the month, the release is not delayed for the feature.  That feature goes into the next release scheduled for two months later.

The name of the release is it's version.  As described in more detail in Versioning, the version number depends on whether the changes are backwards compatible or incompatible.

There is no code freeze for creating a release branch because we as committers only integrate things that pass the Code Review Guidelines.

Once a release branch is created and a release candidate is packaged, release stabilization proceeds as described in Stabilizing a release starting with a two week soak.

Steps to sign a release:

# cd /home/user1
# git clone -b 0.6.0-incubating --single-branch https://git-wip-us.apache.org/repos/asf/incubator-fineract.git apache-fineract-0.6.0-incubating-src
# cd /home/user1
# tar -zcvf apache-fineract-0.6.0-incubating-binary.tar.gz apache-fineract-0.6.0-incubating-binary

 

# cd /home/user1
# tar -zcvf apache-fineract-0.6.0-incubating-src.tar.gz apache-fineract-0.6.0-incubating-src

# cd /home/user1 # gpg --armor --output apache-fineract-0.6.0-incubating-src.tar.gz.asc --detach-sig apache-fineract-0.6.0-incubating-src.tar.gz # gpg --print-md MD5 apache-fineract-0.6.0-incubating-src.tar.gz > apache-fineract-0.6.0-incubating-src.tar.gz.md5 # gpg --print-md SHA512 apache-fineract-0.6.0-incubating-src.tar.gz > apache-fineract-0.6.0-incubating-src.tar.gz.sha # gpg --armor --output apache-fineract-0.6.0-incubating-binary.tar.gz.asc --detach-sig apache-fineract-0.6.0-incubating-binary.tar.gz # gpg --print-md MD5 apache-fineract-0.6.0-incubating-binary.tar.gz > apache-fineract-0.6.0-incubating-binary.tar.gz.md5 # gpg --print-md SHA512 apache-fineract-0.6.0-incubating-binary.tar.gz > apache-fineract-0.6.0-incubating-binary.tar.gz.sha

Finally create a directory with release name (0.6.0-incubating in this example) in https://dist.apache.org/repos/dist/dev/incubator/fineract and add the following files in this new directory.

apache-fineract-0.6.0-incubating-binary.tar.gz.sha

apache-fineract-0.6.0-incubating-binary.tar.gz

apache-fineract-0.6.0-incubating-binary.tar.gz.asc

apache-fineract-0.6.0-incubating-binary.tar.gz.md5

apache-fineract-0.6.0-incubating-src.tar.gz.sha

apache-fineract-0.6.0-incubating-src.tar.gz

apache-fineract-0.6.0-incubating-src.tar.gz.asc

apache-fineract-0.6.0-incubating-src.tar.gz.md5

Next step is to drop mail to dev@fineract.incubator.apache.org about release approval. Once we get sufficient votes, then drop a mail to general@incubator.apache.org

Once release is approved then announce the release to the community.