cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From remibergsma <...@git.apache.org>
Subject [GitHub] cloudstack pull request: implemented upgrade path from 4.6.0 to 4....
Date Sun, 15 Nov 2015 12:48:38 GMT
GitHub user remibergsma opened a pull request:

    https://github.com/apache/cloudstack/pull/1067

    implemented upgrade path from 4.6.0 to 4.6.1

    The 4.6 branch needs an upgrade path to 4.6.1. I looked at how this was done before and
think this will do. Can you give it a second pair of eyes please @DaanHoogland ?
    
    When this is indeed OK, I'll do the same for master for the 4.6.0 -> 4.7.0 path.
    
    I've tried a build and that works: `mvn clean install`
    ```
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 07:33 min
    [INFO] Finished at: 2015-11-15T13:45:58+01:00
    [INFO] Final Memory: 120M/1591M
    [INFO] ------------------------------------------------------------------------
    ```
    
    Once this is a PR, I'll try an actual upgrade from 4.6.0 to 4.6.1-SNAPSHOT.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/remibergsma/cloudstack 460_461_upgrade_path

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1067.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 #1067
    
----
commit 7536fb125d79217e5326ff138423142afe5d14b0
Author: Remi Bergsma <github@remi.nl>
Date:   2015-11-15T12:30:43Z

    implemented upgrade path from 4.6.0 to 4.6.1

----


---
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.
---

Mime
View raw message