Hi Alena! My apologies, I think I got this wrong, will look at fixing it (removing it from 4.2 and putting it into master). But then I have a question - without these changes in 4.2 , if QA tests an upgrade from 4.1 to 4.2, the db upgrade would fail - how do we get around it?? Or should we ask QA not to upgrade 4.1 to 4.2 until 4.1.2 gets released? Will customers ever have a situation where they have to go from version 4.2 to 4.1.2??
Regards, Vijay From: Alena Prokharchyk Sent: Tuesday, August 13, 2013 10:53 AM To: dev@cloudstack.apache.org; Vijayendra Bhamidipati Subject: Re: Change history lost for upgrade sql script schema-412to420.sql It is possible to bring the history of the upgrade file. But why 412 - 42 is in 4.2 branch - thats wrong. As 412 wasn't released yet, and there is a chance that it can be released after 4.2 is out. We should include the "x to y" upgrade path to the y release branch only when the x was released already. So 412-42 should exist in master branch only at this point. Can you please fix it. -Alena. From: Koushik Das <koushik....@citrix.com<mailto:koushik....@citrix.com>> Reply-To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Date: Monday, August 12, 2013 4:04 AM To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>" <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>> Subject: RE: Change history lost for upgrade sql script schema-412to420.sql This is fine but is it possible to bring this history to the renamed file? Also one has to know that there existed a file 410to420.sql. -----Original Message----- From: Devdeep Singh [mailto:devdeep.si...@citrix.com] Sent: Monday, August 12, 2013 4:07 PM To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org> Subject: RE: Change history lost for upgrade sql script schema-412to420.sql See if this helps https://git-wip- us.apache.org/repos/asf/cloudstack/repo?p=cloudstack.git;a=history;f=setu p/db/db/schema- 410to420.sql;h=60335318c7b792a401cab36b8b456e652d47f2a6;hb=e61a38087 d158da51f7b945d16e4749a83512ab5 Regards, Devdeep > -----Original Message----- > From: Koushik Das [mailto:koushik....@citrix.com] > Sent: Monday, August 12, 2013 2:50 PM > To: > cloudstack-...@incubator.apache.org<mailto:cloudstack-...@incubator.apache.org> > Subject: Change history lost for upgrade sql script > schema-412to420.sql > > I noticed that the upgrade sql script (earlier used to be > schema-410to420.sql) has been renamed and in the process all the > change history is lost. Can we ensure as a process to do a proper git > file rename instead of creating a new file so that the changes history > is not lost? In this case is there a way to retrieve the history? > > -Koushik
