Differences between revisions 44 and 50 (spanning 6 versions)
⇤ ← Revision 44 as of 2024-08-01 14:52:16 →
Size: 2190
Editor: RaphaelGomes
Comment:
← Revision 50 as of 2025-02-28 16:08:03 → ⇥
Size: 2453
Editor: Pierre-YvesDavid
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * make sure you are in the `committers` group on mercurial-scm.org
 * make sure you have the admin right on bugzilla
 * make sure your key is uploaded so some public server		  * make sure you have SSH access and are in the `committers` group on mercurial-scm.org
 * make sure you have the admin rights on bugzilla
 * make sure your key is uploaded to some public server
Line 12: Line 12:
 * informs packager that a new key will be used  * inform packagers that a new key will be used for signing
Line 31: Line 31:
 * Create the wheels for MacOS and Windows manually (ping mharbison)
Line 32: Line 33:
  * upload signed release tarball to Pypi with twine
Line 34: Line 34:
  * upload release wheels to Pypi with twine
  * upload release tarball to Pypi with twine
Line 44: Line 46:
 * Update the website with a news about the release
Line 47: Line 50:
 * Update Matrix topic  * Update Matrix topic and IRC topic
Line 49: Line 52:
 * Update your own Mercurial with the new version ;)

Note:

This page is primarily intended for developers of Mercurial.

New Release Manager List

  • make sure you have access to the Mercurial project on PyPi

  • make sure you have SSH access and are in the committers group on mercurial-scm.org

  • make sure you have the admin rights on bugzilla
  • make sure your key is uploaded to some public server
  • inform packagers that a new key will be used for signing

  • get a clone hg-release-tools

Release Checklist

Followed by core developers with accept access to prepare releases.

Things to check:

  • Make sure the latest evolve is compatible
  • Check for queued security patches

  • Pull from Heptapod

  • Check that the Heptapod CI passed

  • Add the release notes in a public changeset
  • Run make-release
    • tag
    • sign
    • build release tarballs
    • make the tag public
  • Create the wheels for MacOS and Windows manually (ping mharbison)
  • Run post-release
    • upload signed release tarball to mercurial-scm.org
    • upload release wheels to Pypi with twine
    • upload release tarball to Pypi with twine
    • update latest.dat file
    • clean-up build
  • publish stable branch
  • push a merge from stable into the default branch to the CI (hence pushing the release changesets)

  • Add Bugzilla version

  • WhatsNew updated (releasenotes, changelog or changes script)

  • UpgradeNotes updated with any (BC) notes

  • For major releases:
    • Create ReleaseX.Y page
    • Add notes for -rc build; replace them when final release is cut
  • Update the website with a news about the release

  • tag and push PythonHglib if there are new changesets

  • Mercurial/NewsItems updated

  • Ping mercurial-packaging@mercurial-scm.org (see template below)

  • Update Matrix topic and IRC topic
    • For rc releases, be sure to note code freeze if there

  • Update your own Mercurial with the new version ;)

Packaging message template: 

To:     mercurial-packaging@mercurial-scm.org
Subject:        Mercurial x.y tagged

Please update your package builds, thanks.
Please also make sure you have the latest evolve version packaged too.

Release notes here: <link to relnotes>

<describe changes in this release important for packagers to note, if any>

CategoryProcess

ReleaseChecklist (last edited 2025-02-28 16:08:03 by Pierre-YvesDavid)