[
https://issues.apache.org/jira/browse/CLOUDSTACK-8672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15934165#comment-15934165
]
ASF GitHub Bot commented on CLOUDSTACK-8672:
--------------------------------------------
Github user karuturi commented on the issue:
https://github.com/apache/cloudstack/pull/1859
When debugging, I have seen issues with humongous commits with little or no
history. They are very difficult to understand.
This is a feature and it need not be backported. so, backporting to
previous releases is out of question. up-porting automatically happens.
If we want to revert the feature, we revert the merge which is very easy to
do.
Also, reverting (for feature stability reasons) is just temporary.
I agree that the number of commits is high. But, the amount of code is also
high and from different authors who wants to keep it this way.
I am +1 with keeping it as is.
I prefer merges with proper history and small logical units.
> NCC Integration with CloudStack
> -------------------------------
>
> Key: CLOUDSTACK-8672
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8672
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Affects Versions: 4.6.0
> Reporter: Rajesh Battala
> Assignee: Rajesh Battala
> Priority: Critical
> Fix For: Future
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
