> 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
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
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
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.
