SRU verification process


#1

During the Ubuntu Stable Release Update (SRU) process of the snapd package we perform the following concrete verifications, based on the general guidelines in the Verification section of [1] and the process adopted by the team [2]:

  • Run automated tests. They can be executed from the release branch with:
$ export SPREAD_MODIFY_CORE_SNAP_FOR_REEXEC=0
$ export SPREAD_TRUST_TEST_KEYS=false
$ export SPREAD_SNAP_REEXEC=0
$ export SPREAD_CORE_CHANNEL=beta
$ spread -v linode:ubuntu-14.04-64 linode:ubuntu-16.04-64 linode:ubuntu-16.10-64 linode:ubuntu-17.04-64
  • Run manual tests described in [3] (those with a “NO” entry in the “Automated?” column) .

  • Review the complete changelog for this release [4]: for each entry verify if it is covered by tests (unit and spread when applicable). If the change affects the user interface and there’s no spread test for it, add an entry to the pending tests list [5] and verify it manually.

  • Verify each of the bugs associated with the SRU from [6] (search for “snapd” in the list, “changelog bugs” column). If the verification can be automated add an entry to the pending tests list [5].

  • Check the autopkgtest results from the excuses page [7]. Sometimes there are regressions caused by flaky tests or temporary failures during the execution, try to reproduce locally.

[1] https://wiki.ubuntu.com/StableReleaseUpdates
[2] https://wiki.ubuntu.com/SnapdUpdates
[3] https://docs.google.com/spreadsheets/d/1blLdL81SpcKBIg8aHX2MJEgGJB9fW0u1Ksm9hbA4ZEQ/
[4] https://github.com/snapcore/snapd/blob/master/packaging/ubuntu-16.04/changelog
[5] https://github.com/snapcore/snapd/wiki/Getting-involved
[6] http://people.canonical.com/~ubuntu-archive/pending-sru.html
[7] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#snapd


SRU verification 2.24