You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/07/01 12:02:20 UTC

[jira] [Commented] (CLOUDSTACK-3300) [DOC] Working with Volume section is missing again in 4.2 and master

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696683#comment-13696683 ] 

ASF subversion and git services commented on CLOUDSTACK-3300:
-------------------------------------------------------------

Commit b68cc3346a8b7c4e49c20d5dbe8e973cbbd6cbce in branch refs/heads/master from [~radhikap]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b68cc33 ]

CLOUDSTACK-3300: Adding patches from cloudstack-1313

                
> [DOC] Working with Volume section is missing again in 4.2 and master
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3300
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3300
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.2.0, Future
>         Environment: platform-independent
>            Reporter: Ryan Lei
>            Priority: Blocker
>             Fix For: 4.2.0, Future
>
>
> In the current Jenkins build, the admin guide is missing this whole section "Working with Volume."
> http://jenkins.cloudstack.org/view/master/job/build-docs-admin-master/
> After browsing the source and history, it seems like CLOUDSTACK-1313 should have been committed to master, too. https://issues.apache.org/jira/browse/CLOUDSTACK-1313
> working-with-volumes.xml in master has never had the missing subsections since it was created. If the removal is not intentional, we should at least have the same working-with-volumes.xml as in 4.1 branch.

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