gt; end of Q1.
>>>> We shouldn't have a problem handling a new unique entry in both with an
>>>> INSERT IGNORE in the 4.12 upgrade script
>>>>
>>>>
>>>> Kind regards,
>>>
have a problem handling a new unique entry in both with an
> >> INSERT IGNORE in the 4.12 upgrade script
> >>
> >>
> >> Kind regards,
> >>
> >> Paul Angus
> >>
> >> paul.an...@shapeblue.com
> >> www.shapeblue.com
in both with an
>> INSERT IGNORE in the 4.12 upgrade script
>>
>>
>> Kind regards,
>>
>> Paul Angus
>>
>> paul.an...@shapeblue.com
>> www.shapeblue.com
>> Amadeus House, Floral Street, London WC2E 9DPUK
>> @shapeblue
&g
GNORE in the 4.12 upgrade script
>
>
> Kind regards,
>
> Paul Angus
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Simon Weller
> Sent: 03 Janua
Street, London WC2E 9DPUK
@shapeblue
-Original Message-
From: Simon Weller
Sent: 03 January 2019 15:23
To: Rohit Yadav ; dev@cloudstack.apache.org
Subject: Re: questions about 4.11 future
Rohit,
Thoughts on this? We can base it on 4.11 or the pending 4.12 master.
- Si
Rohit,
Thoughts on this? We can base it on 4.11 or the pending 4.12 master.
- Si
From: Nathan Johnson
Sent: Wednesday, January 2, 2019 12:23 PM
To: Rohit Yadav
Cc: dev@cloudstack.apache.org
Subject: questions about 4.11 future
First off, is there going
First off, is there going to be a 4.11.3 release?
Assuming so, at what point would it be appropriate to add database migrations?
I have a bug fix I’d like to open a PR on, but it will require a small database
change - namely inserting a record into the configuration table.
Is it appropriate
