lpci

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

  1. Git
  2. lp:~jugmac00/lpci
  3. update-release-process-documentation
  4. Merge into main
Proposed by Jürgen Gmach
Status: Merged
Merged at revision: 89ed52f257526c98ec795fa72efab697f2b6dbfb
Proposed branch: ~jugmac00/lpci:update-release-process-documentation
Merge into: lpci:main
Diff against target: 13 lines (+1/-1)
1 file modified
docs/release-process.rst (+1/-1)
Reviewer Review Type Date Requested Status
Colin Watson (community) Approve
Review via email: mp+415123@code.launchpad.net

Commit message

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

Subscribers

People subscribed via source and target branches