Fred,
The updated doc I saw was this one:
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/index.html
If you look at this section:
It would be nice, if there is an update on the Release Note section, for
upgrading procedure - since system VMs does not start after upgrade from
4.x to 4.2... I know there is bug documented, and should be fixed with
4.2.1.. ?
Best
On 16 October 2013 03:08, Carlos Reategui car...@reategui.com
David,
Would you mind posting the url for the update you reference? I'm looking
at the 4.2 view on buildacloud.com and the last update there was a month
ago. So I assume I'm looking in the wrong place.
Thanks,
Fred
On Mon, Oct 14, 2013 at 2:07 PM, David Nalley da...@gnsa.us wrote:
And just
Thanks for updating it. Without knowing what to look for in the prepare
system vm template section I would not have known that it was updated.
Would it make sense to have a date in the header or footer with the last
content update date for a page?
Also do you know if the upgrade notes in the
And just as a heads up, thanks for help from Prasanna and Travis, I've
published an updated version of the IG for 4.2, hopefully that at
least gets us 'installable'.
--David
On Thu, Oct 10, 2013 at 2:10 PM, David Nalley da...@gnsa.us wrote:
On Thu, Oct 10, 2013 at 1:53 PM, Travis Graham
As you find these things, please create an issue in the JIRA.
At least there will be a record of what needs fixing.
The dispersion of effort and information between the docs and the wiki
needs some discussion.
To an outsider, the wiki seems to be a place that is used to compensate
for the
Agreed Darren,
I would like a nightly build, especially of the api docs. The generic
docs as well would be fine.
there is a jenkins job for those api docs at
https://builds.apache.org/job/cloudstack-apidocs-master/
Can I get karma to see if i can direct the artifacts from that somewhere?
Or
jenkins.buildacloud.org, most jobs that the project uses are on
buildacloud.org. It's fully under our control and I find it more
responsive than builds.a.o
On Thu, Oct 10, 2013 at 02:11:01PM +0200, Daan Hoogland wrote:
Agreed Darren,
I would like a nightly build, especially of the api docs.
That is how it has been done previously - but we recently moved docs
to their own repo to separate the software lifecycle from the docs
lifecycle, and we have already had at least one update pushed to the
docs post-release. The goal is to try and keep this up, and I hope to
publish another set of
What's an acceptable/expected timeframe for rolling out the published fixes
once a patch has made it's way in? Is that something that can be automated
after a successful Jenkins run?
Travis
On Oct 10, 2013, at 1:48 PM, David Nalley da...@gnsa.us wrote:
That is how it has been done previously
On Thu, Oct 10, 2013 at 1:53 PM, Travis Graham tgra...@tgraham.us wrote:
What's an acceptable/expected timeframe for rolling out the published fixes
once a patch has made it's way in? Is that something that can be automated
after a successful Jenkins run?
Travis
It depends on the scope of
On Thu, Oct 10, 2013 at 10:48 AM, David Nalley da...@gnsa.us wrote:
That is how it has been done previously - but we recently moved docs
to their own repo to separate the software lifecycle from the docs
lifecycle, and we have already had at least one update pushed to the
docs post-release.
Agreed Carlos. I've spent all day reading said emails and trying to
wrangle through this problem myself. How to update the templates is here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#
but even getting that to work was an adventure.
On Thu, Oct 10, 2013
It seems like the only way that docs (
http://cloudstack.apache.org/docs/en-US/index.html) are updated is when a
release is done. Is it not possible to have these updated otherwise?
Waiting for the next patch release of the software so that the docs get
updated is causing problems with folks not
Great rant Carlos,
You should get it to the dev list. Actually I'll add the dev list in
now. It makes sense to update the docs also after a release, when bug
in the docs are found these can easily be changed without a full
release cycle of the code itself.
regards,
Daan
On Wed, Oct 9, 2013 at
: Doc Updates
Great rant Carlos,
You should get it to the dev list. Actually I'll add the dev list in now. It
makes sense to update the docs also after a release, when bug in the docs are
found these can easily be changed without a full release cycle of the code
itself.
regards,
Daan
On Wed
-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Sent: Wednesday, October 09, 2013 4:34 PM
To: users@cloudstack.apache.org; car...@reategui.com; dev
Subject: Re: Doc Updates
Great rant Carlos,
You should get it to the dev list. Actually I'll add the dev list in now. It
makes sense
...@reategui.com; dev
Subject: Re: Doc Updates
Great rant Carlos,
You should get it to the dev list. Actually I'll add the dev list in now. It
makes sense to update the docs also after a release, when bug in the docs
are found these can easily be changed without a full release cycle of the
code
When the software was released with a number of reported bugs in the
docs, it was done with the understanding that the 4.2 docs would be
prepared after the release of the software.
Ron
On 09/10/2013 4:34 PM, Daan Hoogland wrote:
Great rant Carlos,
You should get it to the dev list. Actually
Is it not possible to just have a master/latest/head/snapshot version
of the docs on the web page with the individual release too. I do
think it it important to snapshot the documents at the individual
point releases and have those available. But just a latest, fresh
from git link would be nice.
20 matches
Mail list logo
