Agree & Document Ooni Release Process

[tildelowengrimm]

No description provided.

[hellais]

We agreed with @aagbsn that to complete this we have to already have figured out how to make packages and therefore this should be postponed to the release candidate milestone.

We outlined a structure of how this document should look like:

A High Level Overview

== Feature Specification ==

• Specification
• Implementation

== Code Review ==

• Security Review
• MLAB review process

== Build systems & environments ==

• generation of a package
• deciding which platforms to support
• testing the generated package
• uploading the package to the repositories (debian/ubuntu, etc.)

== Testing ==

• integration testing
• unittesting
• code coverage

== Tagging and Signing of a release ==

• versioning semantics
• signing keys

== Release announcement ==

• Write a changelog
• Write a blog post or send a tweet or post to a mailing list

[hellais]

This is now documented here: https://github.com/TheTorProject/ooni-spec/blob/master/Release-Procedure.md