Ideally if the fix involves schema changes then it should go to 4.2. If there is no alternative then 410to411.sql looks like the option. But then the upgrade path becomes complicated. The following needs to be handled 4.1.0 -> 4.2.0, 4.1.1 -> 4.2.0. Or else the upgrade sql script needs to be guarded with "if exists" kind of clause for every schema change so that a single 4.1 -> 4.2 script suffices.
-Koushik > -----Original Message----- > From: Min Chen [mailto:min.c...@citrix.com] > Sent: Wednesday, June 19, 2013 10:14 PM > To: dev@cloudstack.apache.org > Subject: Which file to update for schema change required for 4.1.1? > > Hi there, > > I need to fix a bug for 4.1.1, which requires some schema change. Two > existing files (schema-40to410.sql and schema-410to420.sql) seem not fit > here. In this case, should we create a new schema-410to411.sql for this > purpose? Also, for fix required for 4.1.1, can we directly check into 4.1 > branch > or is it still a controlled checkin? > Thanks for clarification. > > -min
