[
https://issues.apache.org/jira/browse/CLOUDSTACK-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733090#comment-13733090
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-4167:
-----------------------------------------------------------------
Patch posted for review at https://reviews.apache.org/r/13298/
> Put in upgrade paths in master for 4.1.2 and 4.2
> ------------------------------------------------
>
> Key: CLOUDSTACK-4167
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4167
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: Future
> Reporter: Venkata Siva Vijayendra Bhamidipati
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Priority: Minor
>
> In 4.1 branch, the latest version is 4.1.2. So the upgrade path on 4.1 now
> will go thus:
> 4.0.0 -> 4.1.0 -> 4.1.1 -> 4.1.2.
> Now, on the 4.2 branch, it goes thus:
> 4.0.0 -> 4.1.0 -> 4.2.0
> At this point in time, neither 4.2.0 nor 4.1.2 have been released. It is
> unclear which will get released first.
> If 4.1.2 gets released before 4.2.0, we'll need to define an empty upgrade
> path from 4.1.0 to 4.1.2 first, and then another empty upgrade path from
> 4.1.2 to 4.2.0.
> If 4.2.0 gets released before 4.1.2, we will need to define an upgrade path
> from 4.2.0 to 4.1.2 and then another path from 4.1.2 to 4.2.0. Again there
> won't really be any SQL operations to do in these two paths.
> Putting in these upgrade paths tells us which version got released after
> which. In case there are any SQL changes that need to be made, we must put
> those in as well. In any case, the final version when upgrading to 4.2.0 will
> end up at 4.2.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
