launchpad-reviewers team mailing list archive

[Colin Watson <mp+414459@xxxxxxxxxxxxxxxxxx>]

Colin Watson has proposed merging ~cjwatson/lpcraft:release-process-docs into lpcraft:main.

Commit message:
Document current release process

Requested reviews:
  Launchpad code reviewers (launchpad-reviewers)

For more details, see:
https://code.launchpad.net/~cjwatson/lpcraft/+git/lpcraft/+merge/414459

... such as it is.
-- 
Your team Launchpad code reviewers is requested to review the proposed merge of ~cjwatson/lpcraft:release-process-docs into lpcraft:main.

diff --git a/docs/index.rst b/docs/index.rst
index c37c2fc..dc3b958 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -48,3 +48,4 @@ Example configuration
     configuration
     plugins
     CONTRIBUTING
+    release-process
diff --git a/docs/release-process.rst b/docs/release-process.rst
new file mode 100644
index 0000000..8e47351
--- /dev/null
+++ b/docs/release-process.rst
@@ -0,0 +1,24 @@
+Release process
+===============
+
+The lpcraft snap is automatically built for all supported architectures and
+released to the ``edge`` channel in the snap store using a `Launchpad recipe
+<https://launchpad.net/~launchpad/lpcraft/+snap/lpcraft>`_.  Builds run
+shortly after pushes to the ``main`` Git branch; members of the Launchpad
+team can use the "Request builds" button on that recipe if they need updated
+builds urgently.
+
+Most users, as well as default CI builds in Launchpad, should use the
+``stable`` channel rather than the auto-built ``edge`` channel.  People with
+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".
+
+We don't yet have a defined QA process for making new releases to
+``stable``, although it's a good idea to smoke-test that the snap isn't
+obviously broken.
+
+We don't yet use channels other than ``stable`` and ``edge``, though there's
+no particular reason not to do so if they become useful.