Merge pull request #345 from QE-Lab/fix-release-process

Fix release process

Author: razvnane

.github/workflows/assets.yml

@@ -50,7 +50,7 @@ jobs:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       with:
         upload_url: ${{ github.event.release.upload_url }}
-        asset_path: wheelhouse/${{ steps.wheel.outputs.wheel }}
+        asset_path: pybuild/dist/${{ steps.wheel.outputs.wheel }}
         asset_name: ${{ steps.wheel.outputs.wheel }}
         asset_content_type: application/zip
 

.github/workflows/release.yml

@@ -1,6 +1,10 @@
 # OpenQL Framework #
 
-[![Documentation Status](https://readthedocs.org/projects/openql/badge/?version=latest)](https://openql.readthedocs.io/en/latest/?badge=latest) [![Build Status](https://travis-ci.com/QE-Lab/OpenQL.svg?branch=develop)](https://travis-ci.com/QE-Lab/OpenQL)
+[![Documentation Status](https://readthedocs.org/projects/openql/badge/?version=latest)](https://openql.readthedocs.io/en/latest/?badge=latest)
+[![Travis Build Status](https://travis-ci.com/QE-Lab/OpenQL.svg?branch=develop)](https://travis-ci.com/QE-Lab/OpenQL)
+[![GitHub Actions Build Status](https://github.com/QE-Lab/libqasm/workflows/Test/badge.svg)](https://github.com/qe-lab/libqasm/actions)
+[![PyPI](https://badgen.net/pypi/v/qutechopenql)](https://pypi.org/project/qutechopenql/)
+[![Anaconda](https://anaconda.org/qe-lab/openql/badges/version.svg)](https://anaconda.org/qe-lab/openql/)
 
 OpenQL is a framework for high-level quantum programming in C++/Python. The framework provides a compiler for compiling and optimizing quantum code. The compiler produces the intermediate quantum assembly language and the compiled micro-code for various target platforms. While the microcode is platform-specific, the quantum assembly code (qasm) is hardware-agnostic and can be simulated on the QX simulator. For detailed documentation see [here](https://openql.readthedocs.io).
 

README.md

@@ -27,12 +27,15 @@ secrets are configured correctly.
  - Once CI is green, merge the PR into `develop` if there are any changes.
    If no changes were needed, just delete the branch to clean up.
 
- - Push a tag with the appropriate version (customarily `x.y.z` without a `v`
-   in front) for the latest version of `develop` (if the PR had changes and
-   was merged, be sure to pull the changes first).
+ - If needed, also merge to `master`.
 
- - CI will automatically make a complete GitHub release for your tag. It will
-   then run the assets workflow again, now with the new version string baked
+ - Draft a new release through the GitHub interface. Set the "tag version"
+   to the same version you put in `src/version.h`, the title to
+   "Release `version`: `name`", and write a short changelog in the body.
+   For releases that don't go to master, check the "prerelease" box, so it
+   won't show up as the latest release.
+
+ - CI will run the assets workflow again, now with the new version string baked
    into the wheels and packages. When done, these wheels and packages are
    automatically added to the GitHub release, and if the secrets/API keys for
-   PyPI and conda are correct, publish them there.
+   PyPI and conda are correct, CI will publish them there.