How to Release MVD2 0.4

Final release preparation

Prepare annoucement email [DONE MGT]
Prepare annoucement on the blog [DONE MGT]
Update documentation about installation (version number, packages name, list of supported platform) if necessary [NO DOCUMENTATION FOR THE MOMENT]

No last minutes fix allowed [OK]
Test the nightly generated binary packages [DONE MSD]
Update date in RELEASE_NOTES.txt [NO RELEASE NOT FOR THE MOMENT]
Update version number and data version number [DONE MSD]
Before nightly deadline, tag for final release [DONE MSD]
Prepare TGZ source packages (via hg archive) [DONE MSD]
Prepare ZIP source packages (via hg archive) [DONE MSD]
Ensure you named the zipped files with the same convention as the previous release [DONE MSD]
Upload source packages on orfeo-toolbox/packages, move the old ones to the archive [DONE MSD]
Upload the source packages on sourceforge (OTB) [DONE MSD]
Sourceforge (see http://sourceforge.net/apps/trac/sourceforge/wiki/SSH%20Client) :
- Notes :
  - tsocks ssh -t julienmalik,orfeo-toolbox@shell.sourceforge.net create
  - then you can ssh/scp/etc to this shell
  - type sf-help to know where the files dir are located
- Upload the source packages on sourceforge (OTB)
Update status on freecode.com [NOT FOR THE MOMENT]
Do some cleanup in the packages dir on orfeo-toolbox if relevant (keep new release, put release candidate packages in 'archives') [DONE MSD]

Test the generated binary packages in http://www.orfeo-toolbox.org/packages/nightly
Upload following binary packages to orfeo-toolbox and to sourceforge website
- Monteverdi2-windows
- Monteverdi2-MacOS

Generate Ubuntu source packages and upload to launchpad
- generate otb package (provide command)
Send email to mailing list to announce the release [DONE MGT]
Release announcement on the blog [DONE MGT]