You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by Alena Prokharchyk <Al...@citrix.com> on 2014/05/07 19:26:43 UTC

commit 99b4cf788eded0f6f155ff8cda51aeb2e505f764 changes old db upgrade files

Bharat/Kishan,

I’ve looked at the commit 99b4cf788eded0f6f155ff8cda51aeb2e505f764<https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=99b4cf788eded0f6f155ff8cda51aeb2e505f764>, and noticed that you modify old upgrade files - 420to421 - as a part of the commit? That’s not a recommended practice to do so. You should fix all the db upgrade bugs as a part of current db upgrade path (in this case, 4.3–4.4). Plus with your commit, the customers who already upgraded with the bug to 4.2.1, won’t be fixed after upgrading to 4.3.

Please comment on that

-Alena.