There are two things in this actually.
1. the disconnected path goes back more release than assumed
I added tasks since Xenial on the bug here, but even if (for whatever reason) we would decide
not to push that to X/Z it would not affect the Artful SRu to be stalled once verified to work.
2. the open to its own binary on startup, yes I think I have seen those but this is
a) a separate issue to be filed for it.
b) so non severe that no one addressed it so far (might be a nice papercut bug [1])
I'd assume it already exists as severity low/whishlist, then just the tagging has to be done.
Thanks Gordon for the extra info.
There are two things in this actually.
1. the disconnected path goes back more release than assumed
I added tasks since Xenial on the bug here, but even if (for whatever reason) we would decide
not to push that to X/Z it would not affect the Artful SRu to be stalled once verified to work.
2. the open to its own binary on startup, yes I think I have seen those but this is
a) a separate issue to be filed for it.
b) so non severe that no one addressed it so far (might be a nice papercut bug [1])
I'd assume it already exists as severity low/whishlist, then just the tagging has to be done.
[1]: https:/ /wiki.ubuntu. com/One% 20Hundred% 20Papercuts