cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Reategui <car...@reategui.com>
Subject Re: Doc Updates
Date Wed, 16 Oct 2013 01:08:04 GMT
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 Release Notes doc was updated?


On Mon, Oct 14, 2013 at 11:07 AM, David Nalley <david@gnsa.us> wrote:

> 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 <david@gnsa.us> wrote:
> > On Thu, Oct 10, 2013 at 1:53 PM, Travis Graham <tgraham@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 changes. For a document like the release
> > notes, assuming someone already has an updated SVN tree, it shouldn't
> > take more than 30 minutes to update, and it could happen pretty
> > regularly. If it's every document in a single release, that's
> > historically taken the better part of a day. I don't think we'll get
> > away with getting it to happen in an automated fashion, simply because
> > it requires commit access to SVN, which is tied to an individual,
> > which means someone would need to expose their creds, which would be a
> > bad thing.
> >
> > --David
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message