Re: [openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky
> 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
Re: [openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky
On Wed, Sep 05, 2018 at 10:54:25AM +0100, Dougal Matthews wrote: > On 5 September 2018 at 10:52, Dougal Matthews wrote: > > > (Note: I added [release] to the email subject, as I think that will make > > it visible to the right folks.) > > > > Darn. It should have been [stable]. I have added that now. Sorry for the > noise. 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. If y'all push a release note (probably on master too?) then I'm okay with the backport and release Yours Tony. signature.asc Description: PGP signature __ 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
Re: [openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky
I’m also in favour of backporting it because it solves a real production problem. Thanks Renat Akhmerov @Nokia On 5 Sep 2018, 16:55 +0700, Dougal Matthews , wrote: > > On 5 September 2018 at 10:52, Dougal Matthews wrote: > > > > (Note: I added [release] to the email subject, as I think that will > > > > make it visible to the right folks.) > > > > Darn. It should have been [stable]. I have added that now. Sorry for the > > noise. > > > __ > 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 __ 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
Re: [openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky
On 5 September 2018 at 10:52, Dougal Matthews wrote: > (Note: I added [release] to the email subject, as I think that will make > it visible to the right folks.) > Darn. It should have been [stable]. I have added that now. Sorry for the noise. __ 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
