Page History

...

All release artifacts must be signed. In order to sign a release you will need a PGP key. You should get your key signed by a few other people. You will also need to receive their keys from a public key server.   See the Apache release signing page for more details. Please follow the steps defined in Release Sign

Verifying a release candidate

Following are the typical things we need to verify before voting on a release candidate. And the release manager should verify them too before calling out a vote.

• Make sure release artifacts are hosted @https://dist.apache.org/repos/dist/dev/incubator/fineract/
• Release candidates should be in format apache-$project-$version.tar.gz 
• Verify signatures and hashes.  You may have to import the public key of the release manager to verify the signatures. (gpg --recv-key <key id>)
• git tag matches the released bits (diff -rf)
• Can compile successfully from source
• Verify DISCLAIMER, NOTICE and LICENSE (year etc)
• All files have correct headers (Rat check should be clean - gradlew rat)
• No jar files in the source artifacts

Running the vote

Voting has to be done on dev@fineract.incubator.apache.org. You can close the vote after voting period expires and you accumulate sufficient votes.

 Call for voting on dev list (PMC)

To: dev@fineract.incubator.apache.org
Subject: [VOTE] [APACHE FINERACT] 0.7.0-incubating for release

We have created Apache Fineract 0.7.0-incubating release, with the artifacts below up for a vote.
It fixes the following issues: issue details

Source & Binary files : https://dist.apache.org/repos/dist/dev/incubator/fineract/0.7.0-incubating/

Tag to be voted on (rc#): https://git-wip-us.apache.org/repos/asf?p=incubator-fineract.git;a=commit;h=refs/heads/0.7.0-incubating
Fineract's KEYS containing the PGP key we used to sign the release:
https://dist.apache.org/repos/dist/dev/incubator/fineract//KEYS

Note that this release contains source and binary artifacts

Vote will be open for 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Thanks,
$RM 

Rolling out the Release

Close JIRA version

You need to close the release in JIRA so that everyone knows that your version should not be used as "fixVersion" for new bugs. Go to JIRA "Administer project" page and follow "Versions" in left menu. Table with list of all releases should appear, click on additional menu on the right of your release and choose "Release" option. Submit release date and you're done.

...

In order to release you have to checkout release repository located on https://dist.apache.org/repos/dist/release/incubator/fineract and add release artifacts there.

...