[openstack-dev] [Trove] request to backport the fix for bug 1333852 to juno

Ihar Hrachyshka ihrachys at redhat.com
Thu Mar 5 14:42:59 UTC 2015

Hash: SHA1

Not being involved in trove, but some general comments on backports.

On 03/04/2015 08:33 PM, Amrith Kumar wrote:
> There has been a request to backport the fix for bug 1333852 
> (https://bugs.launchpad.net/trove/+bug/1333852) which was fixed in
> Kilo into the Juno release.

It would be easier if you directly link to patches in question.

> The change includes a database change and a small change to the
> Trove API. The change also requires a change to the trove client
> and the trove controller code (trove-api). It is arguable whether
> this is a backport or a new feature; I’m inclined to think it is
> more of an extension of an existing feature than a new feature.

It depends on what is a 'database change' above. If it's a schema
change, then it's a complete no-go for backports. A change to API is
also suspicious, but without details it's hard to say. Finally, the
need to patch a client to utilize the change probably means that it's
not a bug fix (or at least, not an easy one).

Where do those flavor UUIDs come from? Were they present/supported in

> As such, I *don’t* believe that this change should be considered a
> good candidate for backport to Juno but I’m going to see whether
> there is sufficient interest in this, to consider this change to be
> an exception.

Without details, it's hard to say for sure, but for initial look, the
change you describe is too far stretching and has lots of issues that
would make backport hard if not impossible.

Version: GnuPG v1


More information about the OpenStack-dev mailing list