You will need

• Commit rights
• Rights to upload files to sf.net
• SSH Access to ci server

Pre-Release upload

• Adding Software To Mifos guide is followed and the release is not going to break and licence. 
• Decide which binary(package) should be released. (e.g. pick the binary which is used and passed QA testing on CI build)
• inspect the file(s) you are releasing
• if you are releasing a binary archive (such as a .zip or .tar.gz), ensure that the archive explodes into a directory of the same name minus the file extension. For instance, "mifos-v2.0.0.zip" should explode into the subdirectory "mifos-v2.0.0/".
• Create a .CHECKSUMS file using resources/scripts/checksum_release.py (from head/master). Make sure your current, best gpg key is used for signing and it is updated on Release Signatures page

Release upload

• Upload the file(s) to sf.net
• Tag the commit the release was built from
  1. please follow existing conventions for tag and annotationhttp://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head;a=tags
  2. for example:
     1. git tag -s -m "Mifos 2.0.0" 2.0.0 c6e08938e352f3
     2. git push origin 2.0.0

Announcement

Make announcement on the user list.