Comment 91 for bug 1990450

What's the state of this for xenial and bionic?

# Bionic

update-manager | 1:18.04.11 | bionic | source
update-manager | 1:18.04.11.13 | bionic-updates | source
update-manager | 1:18.04.11.21 | bionic-proposed | source
update-manager | 1:18.04.11.22 | bionic/unapproved/e6f5680e | source

The changes file for bionic-unapproved includes versions 18.04.11.16 up to 18.04.11.22, while the changes file for what was accepted into bionic-proposed is from 18.04.11.14 to 18.04.11.21.

You can see the range of versions does not match each other, not even in a continuation scheme. Should bionic-unapproved be rejected?

# xenial

update-manager | 1:16.04.3 | xenial | source
update-manager | 1:16.04.12 | xenial-security | source
update-manager | 1:16.04.17 | xenial-updates | source
update-manager | 1:16.04.18 | xenial-proposed | source
update-manager | 1:16.04.19 | xenial/unapproved/29f0ea91 | source

xenial-proposed has a changes file for just version 16.04.18, and xenial-unapproved's changes file is from 16.04.18 to 16.04.19.

in that form, xenial-unapproved would be ok to consider for sru review and acceptance on top of what is in xenial-proposed currently.

Please state your intentions wrt bionic and xenial considering the above.