Skip to content
Catalin Hritcu edited this page Jun 28, 2020 · 25 revisions

See also Creating binary packages for your platform

  • Find volunteers for creating Mac packages. For Windows and Linux use the weekly-build infrastructure. You can trigger such builds any time via Azure DevOps (aka VSTS). Use the FStar-Binaries-Linux and FStar-Binaries-Windows build definitions.

  • Find volunteers for 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 to master.

  • Create a new branch called v0.9.x.y-release. For alpha or beta releases use v0.9.x.y-alpha-release or v0.9.x.y-beta-release.

  • Bump the version in version.txt

  • Draft a new release on GitHub using the new branch (or a specific commit on that branch). The release title should be the version number optionally followed by some mnemonic. Can use GitHub for a list of changes between two releases or of issues closed between two dates. And now we also have https://github.com/FStarLang/FStar/blob/master/CHANGES.md

Clone this wiki locally