Make sense Flavio, we have approved the spec to delete the downgrade but we can wait a bit more and decide if we warn the deprecation and delete in N or if we do it as long as no one is actually using it.
On Mon, Dec 7, 2015 at 10:01 AM Flavio Percoco <[email protected]> wrote: > On 03/12/15 12:08 +0000, Telles Nobrega wrote: > >Hello all, > > > >we from Trove, want to remove the downgrade fuctionality from our SQL > Schema. > >This was a TC approved spec for all projects across OpenStack[1] and we > need to > >follow this process as well. > >We would like to know if are there anyone using this functionality and > that > >removing it would be a complete mess up for your environment. > >If anyone here is against this please speak up, we are gonna wait 48h and > if we > >get no negative response we will move forward and remove downgrade. > > Hey Telles, > > It's always recommended to wait for a bit more than 48h (1 week?). > > That being said, we (Glance) moved forward with this by adding first a > deprecation warning on downgrades and deferring the deletion to N so > that OPs that are actually using it (no idea if there are) can move > away from it. > > Flavio > > > > >Thanks in advance, > > > > > >[1] http://specs.openstack.org/openstack/openstack-specs/specs/ > >no-downward-sql-migration.html > >-- > >Telles Nobrega > >Software Engineer @ Red Hat > > >_______________________________________________ > >OpenStack-operators mailing list > >[email protected] > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > -- > @flaper87 > Flavio Percoco > -- *Telles Nobrega* Software Engineer @ Red Hat
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
