GitHub user marcaurele opened a pull request:

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

    CLOUDSTACK 9601: Upgrade: change logic for update path for files

    For going from version A to version D, it uses to run the SQL files in
    that order: A -> B -> C -> D -> A-cleanup -> B-cleanup -> C-cleanup ->
    D-cleanup. If you had upgraded each version separatively you would have
    run A -> A-cleanup -> B -> B-cleanup -> C -> C-cleanup -> D ->
    D-cleanup.
    This change the logic to follow the same path if you are jumping over
    versions.
    
    Signed-off-by: Marc-Aurèle Brothier <m...@brothier.org>

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

    $ git pull https://github.com/exoscale/cloudstack fix/CLOUDSTACK-9601

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

    https://github.com/apache/cloudstack/pull/1768.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 #1768
    
----
commit 66a839af4cf10ac65bd66cf4c7875c6fc76d6317
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date:   2016-11-18T14:40:13Z

    Upgrade: change logic for update path for files
    
    For going from version A to version D, it uses to run the SQL files in
    that order: A -> B -> C -> D -> A-cleanup -> B-cleanup -> C-cleanup ->
    D-cleanup. If you had upgraded each version separatively you would have
    run A -> A-cleanup -> B -> B-cleanup -> C -> C-cleanup -> D ->
    D-cleanup.
    This change the logic to follow the same path if you are jumping over
    versions.
    
    Signed-off-by: Marc-Aurèle Brothier <m...@brothier.org>

commit 0dba4be398e0966eb506ef76d2b15bf88c8c0100
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date:   2016-11-18T14:46:30Z

    Cleanup upgrade path from too old version
    
    Today, the schema is created as a version 4.0.0
    
    Signed-off-by: Marc-Aurèle Brothier <m...@brothier.org>

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to