F* release process

Find volunteers for creating and testing packages on Windows, Mac, and Linux
Make sure that F* builds, passes all the tests, and that creating binary packages works well
(Maybe one day) Close all issues that were already fixed (helps getting nicer release notes, but only works well if people actually use the tracker for their work).
Push all changes to the OCaml snapshot
Bump the version in version.txt
Create a new branch called v0.9.x.y
Draft a new release on GitHub using the new branch, the version maybe followed by some mnemonic as the release title, and a description of the changes. Can use GitHub for a list of changes between two releases or of issues closed between two dates.

Have the volunteers create packages for their platform and add them to the release. Make sure the volunteers use the right branch and that the commit field in fstar.exe --version points to the right commit and is not marked dirty.
Have the volunteers test the binaries for their platform https://github.com/FStarLang/FStar/blob/master/INSTALL.md#testing-a-binary-package
At the end of a release, please remember to update the links at: https://www.fstar-lang.org/#download

Provide feedback