This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

Steps to sign a release:

# cd /home/user1
# git clone -b 0.6.0 --single-branch apache-fineract-0.6.0-src
  • Make sure build is happening and all integration tests are passed by following steps defined in
  • Create a binary directory with release version under /home/user1/. In this example the directory name is apache-fineract-0.6.0-binary
  • Build war file and copy into binary directory. Extract LICENSE, NOTICE, DISCLAIMER files from fineract-provider.war and place them in binary directory.
  • Now create a tar file of binary directory with below command. This command will create apache-fineract-0.6.0-binary.tar.gz file in /home/user1 directory.
# cd /home/user1
# tar -zcvf apache-fineract-0.6.0-binary.tar.gz apache-fineract-0.6.0-binary
  • Now move to apache-fineract-0.6.0-src and remove all git configuration directories/files. Remove bin, catalina.base_IS_UNDEFINED, build directories from fineract-provider directory
  • Remove gradle wrapper jar file from apache-fineract-0.6.0/fineract-provider/gradle/wrapper
  • Remove LICENSE_RELEASE, NOTICE_RELEASE files. Rename LICENSE_SOURCE TO LICENSE and NOTICE_SOURCE to NOTICE. Remove binary directory from licenses directory.
  • Now create source tar file with below command. This command with create apache-fineract-0.6.0-src.tar.gz file in /home/user1 directory.


# cd /home/user1
# tar -zcvf apache-fineract-0.6.0-src.tar.gz apache-fineract-0.6.0-src
  • Next step is to create detached signature, checksum with MD5 and SHA with the following commands
# cd /home/user1 
# gpg --armor --output apache-fineract-0.6.0-src.tar.gz.asc --detach-sig apache-fineract-0.6.0-src.tar.gz 
# gpg --print-md MD5 apache-fineract-0.6.0-src.tar.gz > apache-fineract-0.6.0-src.tar.gz.md5 
# gpg --print-md SHA512 apache-fineract-0.6.0-src.tar.gz > apache-fineract-0.6.0-src.tar.gz.sha512 
# gpg --armor --output apache-fineract-0.6.0--binary.tar.gz.asc --detach-sig apache-fineract-0.6.0-binary.tar.gz 
# gpg --print-md MD5 apache-fineract-0.6.0-binary.tar.gz > apache-fineract-0.6.0-binary.tar.gz.md5 
# gpg --print-md SHA512 apache-fineract-0.6.0-binary.tar.gz > apache-fineract-0.6.0-binary.tar.gz.sha512
  • Finally create a directory with release name (0.6.0 in this example) in and add the following files in this new directory.
    • apache-fineract-0.6.0-binary.tar.gz.sha
    • apache-fineract-0.6.0-binary.tar.gz
    • apache-fineract-0.6.0-binary.tar.gz.asc
    • apache-fineract-0.6.0-binary.tar.gz.md5
    • apache-fineract-0.6.0-src.tar.gz.sha
    • apache-fineract-0.6.0-src.tar.gz
    • apache-fineract-0.6.0-src.tar.gz.asc
    • apache-fineract-0.6.0-src.tar.gz.md5
  • Next step is to drop mail to about release approval.
  • Once release is approved then announce the release to the community.
  • Update the website to point to the latest release.

Points to remember:

  • No labels