Hi Karol, my plan is to work at this in January, following the new
backporting process [1].
https://wiki.ubuntu.com/UbuntuBackports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870244
Title:
ec2m
Hi Paride - I think your idea to put this fix in -backports pockets
sounds good. Do you have any idea when the backport for bionic will be
ready?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870244
I put some more thought on the possibility of SRUing this to Bionic and
Focal, and my conclusion is that it's probably not a good idea to
attempt a SRU. The rationale is:
1. This doesn't clearly fit into the SRU requirements [1], as we're not
fixing a bug, but enabling a new feature. I agree it's
** No longer affects: cloud-utils (Ubuntu Hirsute)
** Also affects: cloud-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu Bionic)
Status: New => Triaged
** Changed in: cloud-utils (Ubuntu Bionic)
Assignee: (unassigned) => Paride Le
Would it also make sense to backport to all still-supported LTS releases?
That way companies still using LTS can take advantage of this important AWS
security feature without first having to upgrade all their instances. Just
a thought…
On Mon, Sep 6, 2021 at 8:00 AM Paride Legovini <1870...@bugs.l
This should be fairly simple to SRU to Focal and Hirsute. I added bug
tasks for those and assigned myself.
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-utils (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: cl
