Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1068
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156939746
remi mentioned on slack that master already has 461to470. so, the merge
wont be a problem.
In future, during the first merge after any release, we should take c
Github user karuturi commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156911523
4.6 has 4.6 to 4.6.1 upgrade path
and master has 4.6 to 4.7 upgrade path
once 4.6 is merged to master, wont there be a problem with upgrade path on
mas
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156860838
compiled and started with no errors. tests are running but irrelevant for
this PR: LGTM
---
If your project is set up for it, you can reply to this email and
Github user milamberspace commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156859431
LGTM
Tested on a 4.6.1 to 4.70 with success
2015-11-15 22:00:04,726 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
Cleanup script
/usr/sha
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156845271
This is an `4.6.0` to `4.7.0` upgrade:
```
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.6.0 Code
Version = 4.7.0-SNAPSHOT
INF
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1068#issuecomment-156842157
This is an upgrade from `4.6.1` to `4.7.0`:
```
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.6.1 Code
Version = 4.7.0-SNAPSHOT
GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1068
Make master 4.7.0-SNAPSHOT and implement upgrade paths towards it
This bumps all pom.xml versions to 4.7.0-SNAPSHOT. It also implements
upgrade paths from 4.6.0 and the upcoming 4.6.1 (bran
