Juju SRU and QA plans

[Martin Pitt]

Steve Langasek [2014-10-07 17:14 -0700]:
> Given that Juju is covered by a provisional micro release exception[1], I
> don't understand the ordering concern.  MREs are granted on the condition
> that the upstream release process is sufficient to QA the update, without a
> separate verification step in Ubuntu.

Well, it only means that we don't need individual bug reports, test
cases, and bug fix verification for each issue. We still *do* require
running the regression test plan to ensure that the binary was
correctly built and works with the corresponding release. That of
course can be done in a PPA beforehand as well (and any failure of the
rebuild in *-proposed would then be a really improbable
surprise/disaster). But there still *is* a separate verification step
for MRE SRUs normally.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20141008/1175e617/attachment.pgp>