Skip to content

Latest commit

 

History

History
55 lines (40 loc) · 1.96 KB

RELEASE_CHECKLIST.md

File metadata and controls

55 lines (40 loc) · 1.96 KB
Raw

Release Checklist

Steps to prepare a new release.

Submit a PR to update the version metadata

  • Bump the project(version) value in meson.build
  • Add a corresponding <release>...</release> block to the top of the <releases> section in data/metainfo/org.gnome.Shell.Extensions.GSConnect.metainfo.xml.in
  • Merge the PR to create a release commit

Caution

The AppStream metadata will contain a release date for the new version. If the PR isn't merged immediately, double-check that it matches the current date before merging.

Package the new release

  • Run git pull on the main branch
  • Run meson setup _build .
  • Run meson compile -C _build make-zip

Publish to GitHub Releases

  • Open the New Release template (or click "Draft a new release" from the Releases page)

  • Create a new v## tag matching the new version number

  • Click "Generate release notes" to populate the textarea with an autogenerated list of PRs, as a starting point

  • Clean up & compose the final notes, which may mean...

    • Remove automated PRs (dependabot, Crowdin)
    • Remove purely-internal PRs, like CI, build, or repo-maintenance changes. Anything that affects the repo, but not the package, is probably not relevant to endusers and can be left out.
    • (Optional) Write an introductory "What's New" section, highlighting any notable changes or new features.

  • Attach the _build/[email protected] file

  • Publish the release

Submit to EGO

Once the release is published to GitHub, the attached zip file can also be submitted to extensions.gnome.org by the designated extension author (currently @daniellandau).