wip

SETUP.md

@@ -342,12 +342,13 @@ You can then open the Jupyter notebook server at http://localhost:8888
 
 The process of making a new release and publishing it to pypi is as follows:
 
+First make sure that the tag that you want to add, e.g. `0.6.0`, is added in [reco_utils.py/__init__.py](reco_utils.py/__init__.py). Follow the [contribution guideline](CONTRIBUTING.md) to add the change.
+
 1. Make sure that the code in main passes all the tests (unit and nightly tests).
-2. Update the version number in [reco_utils.py/__init__.py](reco_utils.py/__init__.py)
-3. Create a tag with the version number: e.g. `git tag -a 0.6.0 -m "Recommenders 0.6.0"`.
-4. Push the tag to the remote server: `git push origin 0.6.0`.
-5. When the new tag is pushed, a release pipeline is executed. This pipeline runs all the tests again (unit, smoke and integration), 
+1. Create a tag with the version number: e.g. `git tag -a 0.6.0 -m "Recommenders 0.6.0"`.
+1. Push the tag to the remote server: `git push origin 0.6.0`.
+1. When the new tag is pushed, a release pipeline is executed. This pipeline runs all the tests again (unit, smoke and integration), 
 generates a wheel and upload it to a [GitHub draft release](https://github.com/microsoft/recommenders/releases).
-6. Fill up the draft release with all the recent changes in the code.
-7. Download the wheel locally, this is a wheel that shouldn't have any bug, since it passed all the tests.
-8. Publish the wheel to pypi: `twine upload ms-recommenders*.whl`
+1. Fill up the draft release with all the recent changes in the code.
+1. Download the wheel locally, this is a wheel that shouldn't have any bug, since it passed all the tests.
+1. Publish the wheel to pypi: `twine upload ms-recommenders*.whl`