Skip to content

Commit

Permalink
Forgotten snap reference file
Browse files Browse the repository at this point in the history
  • Loading branch information
Hook25 committed Jul 26, 2023
1 parent 020d7ef commit 5087a5f
Showing 1 changed file with 76 additions and 0 deletions.
76 changes: 76 additions & 0 deletions docs/reference/snaps.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
.. _snap_reference:

===============
Snap Versions
===============

There are several checkbox snaps and channels to choose from. You can
get a full list via ``snap info checkbox``. You can refer to the following
to decide what you should install.

.. _ref_which_snap:

Picking your version
====================

As you may recall from the installation guide, when installing checkbox
you need to pick a frontend and a backend. There are several parameters that
may influence your choice of the best snap for your situation but in general
there are three distinguishing factors in checkbox snaps: base, confinement and
stability.

Base
----

The base of a snap is the underlying version of the operating system
that it uses to run. For example ``checkbox 22.04`` and ``checkbox22``
are built on top of ``Ubuntu22.04``. This is not an 100% accurate
explanation of what a base is but you can use this rule of thumb in your decision.
If you want a more complete explanation of what bases are and how they are built,
refer to this
`blob post from the snapcraft team <https://snapcraft.io/blog/all-about-that-base>`_.

In general we advise to use the version of checkbox that most closely matches the
system that is going to run it. If you are not on an LTS release of Ubuntu or
you are using a completely different operating system, try to match it to
the closest release we have. For example, if you are on ``Ubuntu23.04``,
``checkbox22`` is probably the one you will have to choose.

Confinement
-----------

As you may know, or may learn more from
`the snapcraft documentation <https://snapcraft.io/docs/snap-confinement>`_, a
snap can either use ``strict`` or ``classic`` confinement. Checkbox has a snap
for both models. The strict snaps are called ``ucXX``, the classic ones have a
standard LTS name.

In general we advise to use ``strict`` snap whenever possible.
You are going to need the ``classic`` one whenever the tests you are running
need a binary that is available in your system but not in the ``strict`` snap.

.. note::

This section only applies to the checkbox frontend, the backend snap is always
``strictly`` confined.

Stability
---------

Checkbox uses `semantic versioning <https://semver.org>`_. There are three channels
that you can install from ``edge``, ``beta`` and ``stable``.

If you want a stable version that we are pretty sure that works, use ``stable``, this
version was tested thoroughly via CI and in our lab and is the one that we use for
our `Ubuntu Certified <https://ubuntu.com/certified>`_ program.

If you can trade a little bit of stability for more up-to-date features, you can use
``beta``. This version of checkbox was tested via CI and on a subset of our lab. It
should be as good as ``stable``, but once we are sure it is we will promote it to
that channel.

If you want the most up-to-date possible build of checkbox you can use the
``edge`` channel. This builds are updated daily and contain the latest changes to
the framework. We do not advise to use this channel in production, it is tested
via CI and it is built from the latest commit in the ``main`` branch of the
`Checkbox Repository on github <https://github.com/canonical/checkbox>`_.

0 comments on commit 5087a5f

Please sign in to comment.