You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by remibergsma <gi...@git.apache.org> on 2015/12/21 22:47:57 UTC
[GitHub] cloudstack pull request: Set version 4.8.0-SNAPSHOT in master bran...
GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1268
Set version 4.8.0-SNAPSHOT in master branch
- setnextversion.sh
- upgrade path to `4.8.0` via `4.7.0` -> `4.7.1` as this is the one set in `4.7` branch. Then we also have the next minor release of `4.7` covered.
Build succeeds:
```
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:07 min
[INFO] Finished at: 2015-12-21T22:45:41+01:00
[INFO] Final Memory: 124M/1609M
[INFO] ------------------------------------------------------------------------
```
Will run upgrade test soon and post results.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/remibergsma/cloudstack 480_version
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1268.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1268
----
commit 8f5a2920e8b92f777447c51ccaa0bdfce376fb4a
Author: Remi Bergsma <gi...@remi.nl>
Date: 2015-12-21T21:09:31Z
Updating pom.xml version numbers for release 4.8.0-SNAPSHOT
Signed-off-by: Remi Bergsma <gi...@remi.nl>
commit 117635fb1914f65b0c04a824a099cc127fc25fa6
Author: Remi Bergsma <gi...@remi.nl>
Date: 2015-12-21T21:12:21Z
Update Debian changelog
commit 7c58630867fa617cf36483a19fc090504ba9d076
Author: Remi Bergsma <gi...@remi.nl>
Date: 2015-12-21T21:18:55Z
Implement upgrade path 4.7.1 -> 4.8.0
----
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Set version 4.8.0-SNAPSHOT in master bran...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/1268
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Set version 4.8.0-SNAPSHOT in master bran...
Posted by pdion891 <gi...@git.apache.org>.
Github user pdion891 commented on the pull request:
https://github.com/apache/cloudstack/pull/1268#issuecomment-166435454
LGTM already 4.8 ! :-)
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Set version 4.8.0-SNAPSHOT in master bran...
Posted by remibergsma <gi...@git.apache.org>.
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1268#issuecomment-166436615
@pdube Indeed, as we speed up releases this becomes a real bottleneck. We should handle db upgrades out of the repo. There was some discussion already. Let's see how others solve this problem ;-)
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Set version 4.8.0-SNAPSHOT in master bran...
Posted by remibergsma <gi...@git.apache.org>.
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/1268#issuecomment-166437027
Tested upgrade, works fine:
```
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Grabbing lock to check for database upgrade.
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = 4.7.1 Code Version = 4.8.0-SNAPSHOT
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Database upgrade must be performed from 4.7.1 to 4.8.0-SNAPSHOT
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleaning upgrades because all management server are now at the same version
INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade Upgrade471to480 to upgrade from 4.7.1-4.8.0 to 4.8.0
INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Configuring CloudStack Components
INFO [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) (logid:) Done Configuring CloudStack Components
```
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request: Set version 4.8.0-SNAPSHOT in master bran...
Posted by pdube <gi...@git.apache.org>.
Github user pdube commented on the pull request:
https://github.com/apache/cloudstack/pull/1268#issuecomment-166436287
Code reviewed. Nothing out of the ordinary. LGTM. There must be a better way to do it than to manually add it to each and every migration though.
---
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 enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---