Skip to content

Conversation

@JakeQZ
Copy link
Collaborator

@JakeQZ JakeQZ commented Jul 1, 2024

There don't seem to be any more enhancements in the immediate pipeline, so it would be good to get this out now with the four we have, most or all of which I think have been requested by users.

(I'm not sure I can do the actual release. I've never made one before, and don't know what's involved/needed.)

There don't seem to be any more enhancements in the immediate pipeline,
so it would be good to get this out now with the four we have,
most or all of which I think have been requested by users.

(I'm not sure I can do the actual release.
I've never made one before, and don't know what's involved/needed.)
@JakeQZ JakeQZ added the release PRs for creating a new release label Jul 1, 2024
@JakeQZ JakeQZ added this to the 8.6.0 - Critical Features milestone Jul 1, 2024
@JakeQZ JakeQZ requested a review from oliverklee July 1, 2024 00:46
@JakeQZ JakeQZ self-assigned this Jul 1, 2024
@oliverklee oliverklee merged commit d2fb94a into v8.x Jul 1, 2024
@oliverklee oliverklee deleted the release/8.6.0 branch July 1, 2024 07:33
@oliverklee
Copy link
Collaborator

I've just done the release. These were the steps:

git switch v8.x
git tag
git tag -a -s v8.6.0 -m "Tag version 8.6.0"
git push --tags 

… and then create release on GitHub from the tag, copying the changelog. Also I closed the milestone on GH.

Notes on the commands:

  1. The first git tag is not strictly necessary. I usually do it nonetheless to check that the previous tags are there, and to remind myself of the format (which for the life of me I cannot remember).
  2. The -s switch in the second git tag command means that I GPG-sign the tag (which requires that I've GPG set up for git).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release PRs for creating a new release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants