Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
languagejava
% 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 fineract apache-fineract-$RELEASE-src

...

This release addressed 250 issues.

Readme: https://github.com/apache/fineract/blob/release-$RELEASE/README.md

Release page: https://cwiki.apache.org/confluence/display/FINERACT/$RELEASE+-+Apache+Fineract

...