Comment 2 for bug 1723530

Revision history for this message
James Page (james-page) wrote :

Actually things are a little different with regards to OpenStack packages in Ubuntu; the Debian OpenStack team has been a bit on and off over the last few years, so Ubuntu leads with OpenStack packages rather than the normal sync/merge flow with Debian, with git repositories on Launchpad for the Ubuntu package:

  https://code.launchpad.net/~ubuntu-server-dev/ubuntu/+source/openstack-trove/+git/openstack-trove

I'd suggest the following course of action to get updates to trove in Ocata; As the changes are committed upstream, a point release into Ubuntu zesty (which is the source of trove in the Ocata Cloud Archive) is appropriate.

Preparing the upload for a point release is probably a small amount of effort; however it will need testing in both Zesty and for the Ocata Cloud Archive on Xenial for any regressions. The Ubuntu OpenStack team don't have this capability (as trove remains un-charmed), so someone with capability to test on both of these targets will need to complete this activity to fulfil the requirements of the stable release update process.