...
- dev@fineract.apache.org mailing list membership (and past activity, for credibility..)
- Apache Confluence Wiki Edit permission (for contributing to e.g. improving this page and creating the release notes overview page)
- Apache JIRA full permission (for moving issues to the next release)
- git committer privileges (for creating tags)
- familiarity with locally building the Fineract code (for creating the release ZIP)
- PMC membership (for uploading the release ZIP) - this can of course be delegated
- familiarity with PGP/GPG (for digitally signing the release ZIP)
TODO FINERACT-874 what about the release.sh script? Either clarify its role and when to use it here, or remove it from git.
1. Chose Release Manager (RM)
...
Code Block | ||
---|---|---|
| ||
% git checkout $RELEASE % git tag -a release-$RELEASE -m "Fineract $RELEASE release" #Make sure compiles/tests run fine and rat check is fine (% cd fineract-provider, % gradlew clean integrationTest); run additonally manual tests with the community app % git push origin release-$RELEASE |
Create source and binary artifacts. The steps are defined in Release Sign
...
% cd /fineract-release-preparations % tar -xvf apache-fineract- $RELEASE -src.tar.gz #Do a fresh clone of the tag % git clone https://git-wip-us.apache.org/repos/asf/fineract.git % cd fineract/ % git checkout tags/ release-$RELEASE% cd .. % diff -r
|
...
Code Block | ||
---|---|---|
| ||
svn co https://dist.apache.org/repos/dist/release/fineract fineract-release cdmkdir fineract-release mkdir /$RELEASE/ cp $source_to_your_artifacts fineract-dist-dev/$RELEASE/ svn add $RELEASE/* fineract-release/$RELEASE/ svn add fineract-release/$RELEASE/ svn commit -m "Fineract Release $RELEASE" fineract-release/$RELEASE/ |
You will now get an automated email from the Apache Reporter Service (no-reply@reporter.apache.org), subject "Please add your release data for 'fineract'" to add the release data (version and date) to the database on https://reporter.apache.org/addrelease.html?fineract (requires PMC membership).
Remove git release branch & merge release tag into develop branch
As discussed in FINERACT-1154, now that everything is final, please do the following to remove the release branch (and just keep the tag), and make sure that everything on the release tag is merged to develop and that e.g. git describe
works:
git checkout develop
git branch -D $RELEASE
git push origin :$RELEASE
git checkout develop
git checkout -b merge-$RELEASE
git merge -s recursive -Xignore-all-space $RELEASE
# Manually resolve merge conflicts, if any
git commit
git push $USER
hub pull-request
Update the website
Finally update the https://fineract.apache.org website with the latest release details. The website's HTML source code is available at https://github.com/apache/fineract-site.
...
To: announce@apache.org
CC: dev@fineract.apache.org,user@fineract.apache.org
Subject: [ANNOUNCE] Apache Fineract $RELEASE Release
Hi all,
The
...
Apache
...
Fineract project is pleased to announce
the release of Apache Fineract $RELEASE.
The release is available for download from
https://fineract.apache.org/#downloads
Fineract provides a reliable, robust, and affordable solution for entrepreneurs,
financial institutions, and service providers to offer financial services to the
world’s 2 billion underbanked and unbanked. Fineract is aimed at innovative mobile
and cloud-based solutions, and enables digital transaction accounts for all.
This release addressed 250 issues.
Readme: https://github.com/apache/fineract/blob/$RELEASE/README.md
Release page: https://cwiki.apache.org/confluence/display/FINERACT/$RELEASE+-+Apache+Fineract
...
List of fixed issues:
https://
...
...
secure/ReleaseNote.jspa?version=12344606&styleName=Html&projectId=12319420
For more information on Apache Fineract please visit
project home page: https://fineract.apache.org
The Apache Fineract Team