launchpad-reviewers team mailing list archive

[Jürgen Gmach <mp+415123@xxxxxxxxxxxxxxxxxx>]

Jürgen Gmach has proposed merging ~jugmac00/lpcraft:update-release-process-documentation into lpcraft:main.

Commit message:
update release process documentation

Requested reviews:
  Launchpad code reviewers (launchpad-reviewers)

For more details, see:
https://code.launchpad.net/~jugmac00/lpcraft/+git/lpcraft/+merge/415123
-- 
Your team Launchpad code reviewers is requested to review the proposed merge of ~jugmac00/lpcraft:update-release-process-documentation into lpcraft:main.

diff --git a/docs/release-process.rst b/docs/release-process.rst
index d47dc91..cfa843f 100644
--- a/docs/release-process.rst
+++ b/docs/release-process.rst
@@ -14,7 +14,7 @@ publishing access to the snap in the store can promote revisions to
 ``stable`` (ask Colin Watson for access if you need it).  The easiest way to
 do this across all architectures is to use the store's `Releases page
 <https://snapcraft.io/lpcraft/releases>`_: click on the cog icon next to
-"latest/edge" and select "Promote to: latest/stable".
+"latest/edge", select "Promote/close" and then "Promote to: latest/stable".
 
 Version numbers in snaps are for human consumption (the revision is assigned
 by the store and is what matters to ``snapd``), and there's nothing to stop