Improve release management procedures

[fpietrosanti]

We need definitely to improve our release management procedures in order to be able to bring/show the value of our work to the users.

Currently we manually edit the Changelog (that lead to un-allignment between release and documentation), to manually announce a new release and we are missing archival of all debian package that has been release (with the problem of not being able to test automatically the upgrades procedures).

I think that we should analyze how to move all of globaleaks packaging to bintray in order to achieve:

• history of package release
• notification of releases
• screenshots attached to each release
• cloud hosting of packages (one less requirement)
• having a "Development debian repository" (so that people and CI can also work with -dev packages)

Then we should probably simplify the release procedure so that's a single command line to be executed.

Then we should also semi-automate the way we make announcement of new releases (for example publishing on freecode.com and other opensource resources).

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[fpietrosanti]

We know that we should check how to properly apply digital signatures on debian packages/repo.