[
https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993434#comment-14993434
]
ASF GitHub Bot commented on CLOUDSTACK-8832:
--------------------------------------------
Github user ustcweizhou commented on the pull request:
https://github.com/apache/cloudstack/pull/801#issuecomment-154363971
@mlsorensen I agree with that third-parties can ship their own packages
based on official release. It is more flexible for them. They can release new
packages with new feature/improvement and bug fix, no need to wait for official
cloudstack release.
I also understand their concern that the code difference between their
branch and master branch will become more and more bigger if they cannot merge
most of their codes to main branch. It will be difficult to upgrade to new
cloudstack versio. The upgrade means a lot of work, especially if there is
framework refactoring. I believe many companies have their cloudstack branch
with new features and customized UI , and they face the issue when they want
new features and upgrade to new version.
> Update Nuage VSP plugin to work with Nuage VSP release 3.2
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-8832
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.6.0
> Reporter: Nick Livens
> Assignee: Nick Livens
> Attachments: nuageVspMarvinLogs.tar.gz
>
>
> Nuage VSP 3.2 is being released, we want to bring the plugin up to date for
> this release
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
