Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.8.0 #635

Merged
merged 2 commits into from
Feb 4, 2025
Merged

Release 1.8.0 #635

merged 2 commits into from
Feb 4, 2025

Conversation

wismill
Copy link
Member

@wismill wismill commented Jan 30, 2025

How to make a libxkbcommon release

Steps

Prepare the release

  • Ensure there is no issue in the tracker blocking the release. Make sure
    they have their milestone set to the relevant release and the relevant tag
    “critical”.

  • Ensure all items in the current milestone are processed. Remaining items
    must be explicitly postponed by changing their milestone.

  • Create a release branch: git checkout -b release/vMAJOR.MINOR.PATCH master

  • Update the NEWS.md file for the release, following the corresponding instructions.

  • Bump the version in meson.build.

  • Run meson dist -C build to make sure the release is good to go.

  • Commit git commit -m 'Bump version to MAJOR.MINOR.PATCH'.

  • Create a pull request using this template and ensure all CI is green.

  • Merge the pull request.

  • Tag git pull && git tag --annotate -m xkbcommon-<MAJOR.MINOR.PATCH> xkbcommon-<MAJOR.MINOR.PATCH>.

  • Push the tag git push xkbcommon-<MAJOR.MINOR.PATCH>.

Send announcement email to wayland-devel

Subject: [ANNOUNCE] libxkbcommon MAJOR.MINOR.PATCH

<NEWS & comments for this release>

Git tag:
--------

git tag: xkbcommon-<MAJOR.MINOR.PATCH>
git commit: <git commit sha>

<YOUR NAME>

Update website

  • Pull the latest website repository.

  • Add the doc for the release: cp -r <xkbommon>/build/html doc/<MAJOR.MINOR.PATCH>.
    Check carefully that there is no warning during generation with Doxygen.
    It may be necessary to use another version of Doxygen to get a clean build.
    Building from source using the main branch is also a good option.

  • Update the current symlink: ln -nsrf doc/<MAJOR.MINOR.PATCH> doc/current.

  • Grab a link to the announcement mail from the wayland-devel archives.

  • Update the index.html:

    • "Our latest API- and ABI-stable release ..."
    • Add entry to the releases HTML list.
  • Commit git commit -m MAJOR.MINOR.PATCH.

  • Push git push. This automatically publishes the website after a few seconds.


Fixes #548

@wismill wismill added this to the 1.8.0 milestone Jan 30, 2025
@wismill wismill requested review from bluetech and whot January 30, 2025 14:49
Copy link
Member

@bluetech bluetech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a few wording suggestions.

🥳

@wismill
Copy link
Member Author

wismill commented Jan 30, 2025

@whot may want to have a look too.

@wismill
Copy link
Member Author

wismill commented Feb 4, 2025

Let’s release today.

Reviewing the task, I think it would be better to update the website before the sending the email.

@bluetech do you want to send the email?

@bluetech
Copy link
Member

bluetech commented Feb 4, 2025

@wismill Sure. I'll go ahead and do all of the remaining steps later tonight.

@bluetech bluetech merged commit 76740e0 into master Feb 4, 2025
5 checks passed
@bluetech bluetech deleted the release/v1.8.0 branch February 4, 2025 21:47
@bluetech
Copy link
Member

bluetech commented Feb 4, 2025

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Prepare release 1.8
2 participants