Re: [openstack-dev] [stable][mistral] Asking for stable branch policy exception

2017-10-18 Thread Brad P. Crochet
On Wed, Oct 18, 2017 at 12:34 AM Renat Akhmerov wrote: > Dougal, > > I forgot to mention that explicitly but, yes, #1 is needed only not to > break the sequence of migrations. We can manually fix the migration number > in #2 just for stable/pike but I somewhat don’t

Re: [openstack-dev] [stable][mistral] Asking for stable branch policy exception

2017-10-17 Thread Renat Akhmerov
Dougal, I forgot to mention that explicitly but, yes, #1 is needed only not to break the sequence of migrations. We can manually fix the migration number in #2 just for stable/pike but I somewhat don’t like the idea of having different migration numbers in different branches. It’s a good news

Re: [openstack-dev] [stable][mistral] Asking for stable branch policy exception

2017-10-17 Thread Dougal Matthews
On 17 October 2017 at 09:19, Renat Akhmerov wrote: > Hi, > > We have two patches in Mistral that we need to back port to stable/pike. > However, they are against of stable branch management policy because they > slightly change the DB schema. The patches are the

[openstack-dev] [stable][mistral] Asking for stable branch policy exception

2017-10-17 Thread Renat Akhmerov
Hi, We have two patches in Mistral that we need to back port to stable/pike. However, they are against of stable branch management policy because they slightly change the DB schema. The patches are the following: 1. https://review.openstack.org/#/c/512528/ 2.