[SRU] For Yakkety and Xenial (0.9)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Image |
Fix Released
|
High
|
Unassigned | ||
ubuntu-image (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Tracking bug for SRU of ubuntu-image in Yakkety. I plan to ask for an exception so that future uploads to 16.10 can track 17.04 Zesty.
[Impact]
ubuntu-image 0.8 fixes several problems found during actual use, including LP:
#1632134 and LP: #1632085. These two bugs, and a few other minor issues not
tracked in Launchpad, affects users who try to build snappy images with
ubuntu-image. In particular, being able to set the image size is required for
the common use case of being able to boot a virtual machine with the resulting
built disk image.
I am also asking for an SRU exception for ubuntu-image for several reasons:
* snapd already has an SRU exception: https:/
Because ubuntu-image is built on top of snapd (the latter which does the
communication with the store to get the gadget.yaml spec), it makes sense
for ubuntu-image to *also* have an exception. The gadget.yaml specification
is still undergoing development as more use cases are identified, so
ubuntu-image will need to track changes in snapd.
* ubuntu-image has no reverse dependencies. It's a leaf package in universe
so changes to it will have very minimal impact.
* ubuntu-image is a new tool. People only started using it late in the
Yakkety release cycle so as it sees more use, changes will be likely. It
doesn't make much sense to limit uploads, which will only serve to hobble
the tool in 16.10.
* For now, we want ubuntu-image as released into 16.10, 17.04, and the snap
store to be closely aligned, so that all uses are identical. You may wonder
why we want to upload it to both the snap store and the archive, but this is
useful since end-users may be more inclined to use the snap version, but
official images will use the archive version.
[Test Case]
The QA process for ubuntu-image releases is outlined here:
https:/
[Regression Potential]
It is very unlikely, given the suite of tests we run, that the tool will
regress. More so, if it does, it should be very isolated in its effects, so
it can be quickly fixed with no significant impact on the rest of the archive.
summary: |
- SRU + [SRU] For Yakkety and general SRU exception request |
Changed in ubuntu-image: | |
milestone: | none → 0.8 |
importance: | Undecided → High |
Changed in ubuntu-image: | |
milestone: | 0.8 → 0.9 |
Changed in ubuntu-image: | |
status: | New → Fix Released |
summary: |
- [SRU] For Yakkety and Xenial + [SRU] For Yakkety and Xenial (0.9) |
Changed in ubuntu-image (Ubuntu): | |
status: | New → Fix Released |
0.9 should go to Yakkety and Xenial.