On Tue, Sep 2, 2014 at 9:34 AM, Wido den Hollander <w...@widodh.nl> wrote: > > > On 09/02/2014 03:30 PM, sebgoa wrote: >> >> >> On Sep 2, 2014, at 3:20 PM, Rohit Yadav <rohit.ya...@shapeblue.com> wrote: >> >>> Hi, >>> >>> I’m going through list of issues that affect 4.3.0 and 4.3.1 and >>> cherry-picking those which are already fixed elsewhere. This is the issue >>> which would involve some modifications to the schema: >>> https://issues.apache.org/jira/browse/CLOUDSTACK-6756 >>> >>> @Sebatien: can you please take a look at this bug and cherry-pick if we >>> want it in 4.3.1? >>> >> >> I have always been of the impression that we should not have any schema >> changes in minor releases even if it fixes bugs ? >> > > I thought so as well. Since how are people going to upgrade to 4.4.1 from > 4.3.1? > > Wido >
I agree - how will users upgrade from 4.3.1 to 4.4.x or later - schema changes aren't necessarily going to screw up the upgrade process, but certainly have a high likelihood of doing so. What happens when 4.3.0-to-4.4.0.sql runs? The table already exists - and upgrade will puke. 4.4.0 is already released; so not like you can roll that change back. --David
