Release Sign

Steps to sign a release:

• As a release manager, I believe you should have created signing key by following Apache documentation (https://www.apache.org/dev/openpgp.html#key-gen-generate-key). In this example  I am considering 0.6.0-incubating is the release branch and current working directory is /home/user1.
• Prepare the release notes in Release Folders
• Clone release branch with command

# 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

• Make sure build is happening and all integration tests are passed by following steps defined in readme.md
• Create a binary directory with release version under /home/user1/. In this example the directory name is apache-fineract-0.6.0-incubating-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-incubating-binary.tar.gz file in /home/user1 directory.

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

• Now move to apache-fineract-0.6.0-incubating-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-incubating/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-incubating-src.tar.gz file in /home/user1 directory.

# cd /home/user1
# tar -zcvf apache-fineract-0.6.0-incubating-src.tar.gz apache-fineract-0.6.0-incubating-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-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.

Points to remember:

• Sign the release with apache mail id
• Send a mail for the release approval on dev@fineract.incubator.apache.org mailing list. Format of the email can be found at http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201701.mbox/%3CCAOSe2ysBL1pS6YMSbSHS-BT1PPb29K-ZuGqYBd2igepQSFMm%2Bg%40mail.gmail.com%3E
• Once we get sufficient votes, close the vote by dropping an email to dev@fineract.incubator.apache.org mailing list. The format of the email can be found at http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201701.mbox/%3CCAOSe2yuvdNRkt1cAbGQcEwdWVgTpanz7kS5fAQUsnsZZWrRhCw%40mail.gmail.com%3E
• Next drop an email to general@incubator.apache.org mailing list for the release approval from IPMC members. The format of the email can be found at http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201612.mbox/%3CCAOSe2yukqYvDpdLm0y4x2bbp7C6fcdjRiFKr0gGrBR%2BteZq0nQ%40mail.gmail.com%3E
• Once we get at least 3 binding votes, close the vote by dropping an email to general@incubator.apache.org mailing list. The format of the email can be found at http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201612.mbox/%3CCAOSe2yvtsYd4xn67GZs4umFuEz5Ezc17LnE34ju7X2Y%3Dt1Mw4g%40mail.gmail.com%3E
• Once release is approved, copy the release artifacts to https://dist.apache.org/repos/dist/release/incubator/fineract/0.6.0-incubating and then announce the release by dropping an email to announce@apache.org, general@incubator.apache.org. The format of the email can be found at http://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201612.mbox/%3CCAOSe2yvu7J8Xs4eJAoi4uN888w0bDo-%3DNnd_J%2BD9VC6gRd8Gog%40mail.gmail.com%3E