From 61211bda33d1fb202162ff2a5ac7930468353a53 Mon Sep 17 00:00:00 2001 From: Eric Kalosa-Kenyon Date: Tue, 11 May 2021 14:28:12 -0700 Subject: [PATCH] improved release process --- Release-process.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/Release-process.md b/Release-process.md index e596b1d..a88ccd8 100644 --- a/Release-process.md +++ b/Release-process.md @@ -1,6 +1,9 @@ -To create a new release of GPy: -1. Update the semantic versioning in `GPy/__version__.py` -2. Create a PR from your fork to `SheffieldML/GPy:devel` -3. Once that's merged, create a PR from `SheffieldML/GPy:devel` to `SheffieldML/GPy:deploy` +To create a new release of GPy, you must be a maintainer of the repository. -Upon merging the PR in step (3) above, the `deploy` section in `.travis.yml` will be executed to push the package built in CI to PyPi. \ No newline at end of file +The steps required to release are: +1. Update the semantic versioning in `GPy/__version__.py` +2. Tag the `devel` branch using `git tag v1.2.3 && git push --tags` +3. Open a PR from `devel` to `deploy` on the commit you tagged in (2) +4. Once at least one other maintainer has agreed that it's ready, merge the PR into `deploy` + +Upon merging the PR in step (4) above, the `deploy` section in `.travis.yml` will be executed to push the package built in CI to PyPi. \ No newline at end of file