Faasm Releases

    See what's going into the release in the .

    1. Prepare release artifacts

    The sysroot, toolchain and runtime root are all tied to a given release. You must create therelease versions locally before proceeding.

    To do this, you can download the versions from the current release, then apply any changesfor this release (if there are any), i.e.:

    It's worth reading through the notes if you need to change thetoolchain/ core libraries themselves.

    Version needs to be updated in:

    • VERSION at the project root
    • Any kubernetes config files in that specify image names

    This can usually be done with a find-and-replace on the current version number.

    3. Create the Github release

    Now check the draft release. If it's ok:

    You can rebuild all the containers for the given release with:

    5. Create a PR

    Create a PR from your branch, this will then run through the tests for the newrelease. If it's green, you can merge it into master.