incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jessica Tomechak <>
Subject [DOC] How to verify a doc bug fix? (CLOUDSTACK-683)
Date Mon, 14 Jan 2013 21:07:55 GMT
Joe's comment in the bug CLOUDSTACK-683 makes me think that ACS is not pushing the docs to
the website after every successful doc build. Please correct if I'm mistaken about that. I
don't see any "updated on..." date stamp on the docs at the site, so I can't tell at a glance.

I think we are doing a doc build after every checkin, though, right? Which would make the
build server the right place to look for the latest docs when verifying a doc bug fix.

Of course, anyone who has Publican installed and knows how to use it could verify by pulling
the latest from the repo and doing a local build.

Is there any one way that we'd like to agree on for verifying doc bugs?

On a side note - if we are not pushing doc fixes to the website in real time, I wonder why
not? And can we please add a date stamp -- is it difficult to do so?

Jessica T.

-----Original Message-----
From: Radhika Nair (JIRA) [] 
Sent: Thursday, January 10, 2013 8:54 PM
Subject: [jira] [Updated] (CLOUDSTACK-683) Image Is Missing in the Accessing VM Section


Radhika Nair updated CLOUDSTACK-683:

    Attachment: access-vm.png
> Image Is Missing in the Accessing VM Section
> --------------------------------------------
>                 Key: CLOUDSTACK-683
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.0.0
>            Reporter: Radhika Nair
>            Assignee: Joe Brockmeier
>            Priority: Minor
>             Fix For: 4.0.1, 4.1.0
>         Attachments: access-vm.png
> At 
> 0.0-incubating/html/Admin_Guide/accessing-vms.html
> View Console image file is not displayed.

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:
View raw message