digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 09:17:43 +03:00
Code Issues Projects Releases Wiki Activity
59f480d978
daml/release/RELEASE.md
Gary Verhaegen 59f480d978 prepare release note for next release (#443)
2019-04-12 16:17:31 +02:00

1.6 KiB
Raw Blame History

Making a Release

  1. Update https://github.com/digital-asset/daml/docs/source/support/release-notes.rst by adding a new header for the new version above any changes since the last version.

  2. Make a PR that only bumps the version number in the VERSION file. It is important that the PR only changes the VERSION file.

  3. Squash the PR.

  4. Once CI has passed for the corresponding master build, the release should be available on bintray and GitHub, as well as properly tagged.

  5. Activate the new version with da use VERSION. Note that it will not be picked up by da upgrade at this point.

  6. Run through the manual test plan described in https://docs.google.com/document/d/16amcy7bQodXSHjEmKhAUiaPf6O92gUbch1OyixDEvSM/edit?ts=5ca5be00.

  7. If it passes, the release should be made public. This currently consists of two steps:

    1. Tag the release as visible-external on Bintray. This step can only be done by someone with permissions to set tags on Bintray. After this step the release will be picked up by da upgrade.

    2. Trigger the CircleCI jobs to create the Docker images. To do so, go to https://circleci.com/gh/DACH-NY/workflows/damlc-docker/tree/master and click "rerun" on "master / Main Variant" and on "master / CircleCI Variant". Once the jobs have passed, you should see two new images on https://hub.docker.com/r/digitalasset/daml-sdk/tags.

    3. Publish the draft release on GitHub by going to the releases page and clicking the Edit button for the relevant release.