13:07 <rbasak> bdmurray: opinion on releasing bug 1611816 to xenial-updates? It's not verified on Yakkety, and it seems unlikely that anyone will. So that would create a feature regression on Xenial->Yakkety upgrade ("any such feature must then also be added to any newer supported Ubuntu release")
13:08 <rbasak> So should I hold releasing pending verification of Yakkety as well?
@David, thank you for verifying 2:6.4-1ubuntu1.1 on Xenial for us. I'm not sure if I should release to xenial-updates if I cannot also release to yakkety-updates, and I've asked the question. In the meantime, if you could verification the package in yakkety-proposed anyway, that would help regardless.
13:07 <rbasak> bdmurray: opinion on releasing bug 1611816 to xenial-updates? It's not verified on Yakkety, and it seems unlikely that anyone will. So that would create a feature regression on Xenial->Yakkety upgrade ("any such feature must then also be added to any newer supported Ubuntu release")
13:08 <rbasak> So should I hold releasing pending verification of Yakkety as well?
@David, thank you for verifying 2:6.4-1ubuntu1.1 on Xenial for us. I'm not sure if I should release to xenial-updates if I cannot also release to yakkety-updates, and I've asked the question. In the meantime, if you could verification the package in yakkety-proposed anyway, that would help regardless.