[openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky

Pierre Gaxatte pierre.gaxatte at gmail.com
Fri Sep 7 07:21:43 UTC 2018

> Backporting a migration like that is OK as long as you don't skip
> migrations, that is to say revision '030' of the database should be the
> same on all branches.  Given we've only just released rocky I expect
> that will be the case here.
> You absolutely must have a release note and call it out as upgrade impact
> and of course this is a minor release not a patch release.
The release note was not in the initial change so here it is:

Any input is welcome as the wording and content might not be exactly
what you expect.


More information about the OpenStack-dev mailing list