Skip to content

F* release process

Jump to bottom Edit New page
Catalin Hritcu edited this page May 4, 2018 · 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 VSTS. Use the FStar-BinaryBuild-Linux and FStar-BinaryBuild-Windows 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

  • Bump the version in version.txt

  • Create a new branch called v0.9.x.y (or a tag, but branch works better?)

  • 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.

Add a custom footer
Add a custom sidebar
Clone this wiki locally