cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nitin Mehta <Nitin.Me...@citrix.com>
Subject Re: Reverting 17267794adb2bab923fb20515a7b943780d61921
Date Mon, 05 Aug 2013 06:29:06 GMT
Should we not try and enforce it through git ?

On 02/08/13 10:44 PM, "Alex Huang" <Alex.Huang@citrix.com> wrote:

>Ok...i spoke too soon.  Just talked with Prasanna.  He pointed out that
>it's a large change that's been in since May.  So I won't revert it.  But
>the rule is no one can change create-schema.sql until the community
>decided we want to based off of a new copy of the create-schema.
>
>--Alex
>
>> -----Original Message-----
>> From: Alex Huang [mailto:Alex.Huang@citrix.com]
>> Sent: Friday, August 2, 2013 10:01 AM
>> To: Saksham Srivastava
>> Cc: dev@cloudstack.apache.org
>> Subject: Reverting 17267794adb2bab923fb20515a7b943780d61921
>> 
>> Saksham,
>> 
>> I'm reverting commit id: 17267794adb2bab923fb20515a7b943780d61921 in
>> master.
>> 
>> It changed the create-schema.sql.  We've established since 4.1 that
>>create-
>> schema.sql should not be changed and everything done through upgrades.
>>I
>> believe this commit causes a fresh deployment to fail.
>> 
>> --Alex


Mime
View raw message