Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BD27711427 for ; Tue, 2 Sep 2014 16:04:42 +0000 (UTC) Received: (qmail 56258 invoked by uid 500); 2 Sep 2014 16:04:42 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 56207 invoked by uid 500); 2 Sep 2014 16:04:42 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 56196 invoked by uid 99); 2 Sep 2014 16:04:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2014 16:04:41 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rohit.yadav@shapeblue.com designates 213.199.154.78 as permitted sender) Received: from [213.199.154.78] (HELO emea01-db3-obe.outbound.protection.outlook.com) (213.199.154.78) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Sep 2014 16:04:15 +0000 Received: from DBXPR07MB480.eurprd07.prod.outlook.com (10.141.231.154) by DBXPR07MB478.eurprd07.prod.outlook.com (10.141.231.147) with Microsoft SMTP Server (TLS) id 15.0.1015.19; Tue, 2 Sep 2014 16:04:18 +0000 Received: from DBXPR07MB480.eurprd07.prod.outlook.com ([10.141.231.154]) by DBXPR07MB480.eurprd07.prod.outlook.com ([10.141.231.154]) with mapi id 15.00.1015.018; Tue, 2 Sep 2014 16:04:13 +0000 From: Rohit Yadav To: "dev@cloudstack.apache.org" CC: "fgaudreault@cloudops.com" Subject: Re: Cherry-picking fix that may change 4.3.1 schema Thread-Topic: Cherry-picking fix that may change 4.3.1 schema Thread-Index: AQHPxrCZ9Mz5v2GvuEyVjI+cgiT105vt1rKAgAABNoCAABG4AIAAAu6AgAABogCAAAG3AIAAAdMAgAAF84CAAAWmAIAABF4A Date: Tue, 2 Sep 2014 16:04:12 +0000 Message-ID: <5035838F-94DE-4DC9-9052-4FE542A8785A@shapeblue.com> References: <5405C76F.3050807@widodh.nl> <3F69D593-FC40-4572-86B9-1D3BBE2D5D24@shapeblue.com> <5405DA20.8050905@cloudops.com> <1719A8EC-CE4F-4A33-9ADF-E42B84D226AE@shapeblue.com> <5405DD18.9070001@cloudops.com> <84E5B8E9-FE53-456B-B06F-18C941EF509F@shapeblue.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.1878.6) x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [178.199.176.194] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 0322B4EDE1 x-forefront-antispam-report: SFV:NSPM;SFS:(6009001)(199003)(13734003)(377454003)(24454002)(189002)(51704005)(92726001)(89996001)(86362001)(2351001)(77982001)(79102001)(66066001)(20776003)(4396001)(64706001)(50226001)(81542001)(80022001)(74662001)(83072002)(104166001)(46102001)(87936001)(88136002)(101416001)(92566001)(85852003)(93916002)(33656002)(90102001)(77156001)(15975445006)(105586002)(15202345003)(15395725005)(62966002)(57306001)(36756003)(83716003)(85306004)(74502001)(76482001)(81342001)(93886004)(76176999)(110136001)(107046002)(50986999)(95666004)(19580395003)(82746002)(19580405001)(2656002)(99396002)(31966008)(83322001)(21056001)(106356001)(87286001)(106116001)(2501002)(104396001);DIR:OUT;SFP:;SCL:1;SRVR:DBXPR07MB478;H:DBXPR07MB480.eurprd07.prod.outlook.com;FPR:;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG:en; Content-Type: text/plain; charset="Windows-1252" Content-ID: <1B6B80C39910254C8F0FAF7BEF060DE7@eurprd07.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: shapeblue.com X-Virus-Checked: Checked by ClamAV on apache.org If you=92re not going to read anything because the thread has gone too long= already, read this: 4.4.0 is already out there, if we release 4.3.1 there is no way people can = upgrade to 4.4.0 as the upgrade paths exist in the 4.4.0 release itself whi= ch does not know about 4.3.1 On 02-Sep-2014, at 5:48 pm, Will Stevens wrote: > @Rohit > I think we are playing with fire here a bit. DB changes should be made o= n > major releases and we should try to avoid DB changes on minor releases > because of this type of problem. We have to keep the upgrade paths as > clean as possible because we don't want people running into issues when > they upgrade their prod boxes. > > I think we are going to have a problem with this one because I think the > 4.4.1 branch is going to be released before the 4.3.1 branch, so the > upgrade path will be broken. My understanding is that the 4.4.1 branch i= s > planned to be launched on Monday (Sept 8th), so I expect there will be a > problem with the upgrade path if we implement this change in 4.3.1. That= s > my two cents anyway=85 Sorry to break you this, the issue I=92m raising here has always existed be= fore. Just that it was not widely shared and was silently fixed by develope= rs. This is also the first time that we=92re planning to release a minor versio= n from previous major release. That is we already released 4.4.0 and now we= =92re going to release 4.3.1. Database upgrade paths from previous releases are only added in next releas= es. And, you may go look at the code to see that all minor upgrades do intr= oduce some db changes and not just read emails. Sometime they don=92t have = to put an explicit schema-AtoB.sql and their cleanup files. In any case, due to the way we release ACS. People won=92t be able to upgra= de from 4.3.1 to 4.4.0 anyway. Regards, Rohit Yadav Software Architect, ShapeBlue M. +41 779015219 | rohit.yadav@shapeblue.com Blog: bhaisaab.org | Twitter: @_bhaisaab Find out more about ShapeBlue and our range of CloudStack related services IaaS Cloud Design & Build CSForge =96 rapid IaaS deployment framework CloudStack Consulting CloudStack Infrastructure Support CloudStack Bootcamp Training Courses This email and any attachments to it may be confidential and are intended s= olely for the use of the individual to whom it is addressed. Any views or o= pinions expressed are solely those of the author and do not necessarily rep= resent those of Shape Blue Ltd or related companies. If you are not the int= ended recipient of this email, you must neither take any action based upon = its contents, nor copy or show it to anyone. Please contact the sender if y= ou believe you have received this email in error. Shape Blue Ltd is a compa= ny incorporated in England & Wales. ShapeBlue Services India LLP is a compa= ny incorporated in India and is operated under license from Shape Blue Ltd.= Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and= is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a c= ompany registered by The Republic of South Africa and is traded under licen= se from Shape Blue Ltd. ShapeBlue is a registered trademark.