From 48ddd551c71f4fed3fed256ee8770b5df197d5f2 Mon Sep 17 00:00:00 2001 From: sebastian-berlin-wmse <36327337+sebastian-berlin-wmse@users.noreply.github.com> Date: Thu, 4 Jul 2024 10:15:45 +0200 Subject: [PATCH] Add a couple of clarifications to the release process --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d9443f0..b5fecb2 100644 --- a/README.md +++ b/README.md @@ -92,8 +92,8 @@ To avoid having to unzip the extension in the corresponding directory every time - Make sure you are on the `master` branch and it is up to date (`git pull`) - Open `pom.xml` and set the version to the desired version number, such as `0.1.0` -- Commit and push those changes -- Add a corresponding git tag, with `git tag -a v0.1.0 -m "Version 0.1.0"` (when working from GitHub Desktop, you can follow [this process](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags) and manually add the `v0.1.0` and `Version 0.1.0` tags) +- Commit and push those changes to master +- Add a corresponding git tag, with `git tag -a v0.1.0 -m "Version 0.1.0"` (when working from GitHub Desktop, you can follow [this process](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags) and manually add the `v0.1.0` tag the description `Version 0.1.0`) - Push the tag to GitHub: `git push --tags` (in GitHub Desktop, just push again) - Create the zip file for the release: `mvn package` - Create a new release on GitHub at https://github.com/OpenRefine/CommonsExtension/releases/new, providing a release title (such as "Commons extension 0.1.0") and a description of the features in this release. Upload the zip file you generated at the previous step as an attachment (it can be found in the `target` subfolder of your local copy of the repository).