Merge ~jugmac00/lpci:update-release-documentation into lpci:main

Proposed by Jürgen Gmach
Status: Merged
Merged at revision: 5949872e3d66c6c30863bb4e5a0f543a099d26bc
Proposed branch: ~jugmac00/lpci:update-release-documentation
Merge into: lpci:main
Diff against target: 12 lines (+1/-0)
1 file modified
docs/release-process.rst (+1/-0)
Reviewer Review Type Date Requested Status
Colin Watson (community) Approve
Review via email: mp+415169@code.launchpad.net

Commit message

Add last step to the release process documentation

To post a comment you must log in.
Revision history for this message
Colin Watson (cjwatson) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/docs/release-process.rst b/docs/release-process.rst
2index cfa843f..49c7932 100644
3--- a/docs/release-process.rst
4+++ b/docs/release-process.rst
5@@ -15,6 +15,7 @@ publishing access to the snap in the store can promote revisions to
6 do this across all architectures is to use the store's `Releases page
7 <https://snapcraft.io/lpcraft/releases>`_: click on the cog icon next to
8 "latest/edge", select "Promote/close" and then "Promote to: latest/stable".
9+Finally, hit the "Save" button in the top right corner to apply the changes.
10
11 Version numbers in snaps are for human consumption (the revision is assigned
12 by the store and is what matters to ``snapd``), and there's nothing to stop

Subscribers

People subscribed via source and target branches