Ah, that would be fine, too.
(2013/06/22 1:39), Min Chen wrote:
I don't get this. Based on my previous question on the dev list, we should
create a new schema-410to411.sql and Upgrade410to411 to handle any upgrade
from 4.1.0 to 4.1.1, that is how I made the commit in 4.1 for
CLOUDSTACK-3015
(https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=11cfc0
34e0b45cf032c1e9dcfe32021fb73789d5). Why do we need to change existing
Upgrade40to41 file?
Thanks
-min
On 6/20/13 6:31 PM, "Hiroaki KAWAI" <ka...@stratosphere.co.jp> wrote:
I found there is an issue about versioning.
When we cut 4.1.1 release, we have to patch like this:
-----------------------
diff --git a/server/src/com/cloud/upgrade/dao/Upgrade40to41.java
b/server/src/com/cloud/upgrade/dao/Upgrade40to41.java
index 9e386b9..89f54bc 100644
--- a/server/src/com/cloud/upgrade/dao/Upgrade40to41.java
+++ b/server/src/com/cloud/upgrade/dao/Upgrade40to41.java
@@ -39,7 +39,7 @@ public class Upgrade40to41 implements DbUpgrade {
@Override
public String getUpgradedVersion() {
- return "4.1.0";
+ return "4.1.1";
}
@Override
-----------------------
(2013/06/06 3:22), Musayev, Ilya wrote:
Hi All,
Sorry I was a bit disconnected from the community - as my $dayjob kept
me very busy.
I would like to start of this thread to keep track of bugfixes we need
to back port from 4.1 to 4.1.1 release.
Please use this thread and reference bug fixes we need to add into
4.1.1, I will be creating a new 4.1.1 branch/tag shortly.
Regards
ilya
