> 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: https://review.openstack.org/#/c/600018
Any input is welcome as the wording and content might not be exactly what you expect. Regards, Pierre __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
