Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of cryan@harmonia.com designates
 207.46.163.153 as permitted sender)
From: "Christopher M. Ryan" <cryan@harmonia.com>
To: "users@cloudstack.apache.org" <users@cloudstack.apache.org>,
	"carlos@reategui.com" <carlos@reategui.com>, dev <dev@cloudstack.apache.org>
Subject: RE: Doc Updates
Thread-Topic: Doc Updates
Thread-Index: AQHOxS2c5jInpjzt+U+2QV5xhwIuB5ns03AAgAAB4PA=
Date: Wed, 9 Oct 2013 21:01:01 +0000
Message-ID: 
 <b325b427d8124f56a4338450e60715a1@BN1PR01MB231.prod.exchangelabs.com>
References: 
 <CAMbNGRUvnQ2PFTYYH1_Oq_R8fp0fd0dz1AZzGiYJ60D4kiG3RQ@mail.gmail.com>
 <CAGQtxva7gDRLpCzgykGuwcCrtVP1xMBaPSBQ5z6xvDX6wDyayQ@mail.gmail.com>
In-Reply-To: 
 <CAGQtxva7gDRLpCzgykGuwcCrtVP1xMBaPSBQ5z6xvDX6wDyayQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1 on this.=20
I find management hard to please when I persuade changing to a new technolo=
gy only to have issues related to documentation. This prolongs deployment a=
nd doesn't help with the already difficult management decision. It took us =
a month to switch to CloudStack and almost a week to begin defending the ch=
oice because of outdated documentation. This was of course before the donat=
ion to apache, since then it's been a lot easier and management isn't so co=
ncerned. but none the less, publicly facing documentation, I feel, should b=
e kept current, to include bug fixes.=20

Chris Ryan
Harmonia Holdings Group, LLC
404 People Place, Suite 402
Charlottesville, VA 22911
Office:=A0(434) 244-4002


-----Original Message-----
From: Daan Hoogland [mailto:daan.hoogland@gmail.com]=20
Sent: Wednesday, October 09, 2013 4:34 PM
To: users@cloudstack.apache.org; carlos@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. I=
t 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 10:24 PM, Carlos Reategui <creategui@gmail.com> wrot=
e:
> It seems like the only way that docs (
> http://cloudstack.apache.org/docs/en-US/index.html) are updated is=20
> when a release is done.  Is it not possible to have these updated otherwi=
se?
>  Waiting for the next patch release of the software so that the docs=20
> get updated is causing problems with folks not being able to get=20
> CloudStack installed properly and therefore gives them a bad=20
> impression of the maturity of CloudStack.
>
> It makes no sense to me why there are multiple versions of documents=20
> for each of the point releases (currently there is 4.0.0, 4.0.1,=20
> 4.0.2, 4.1.0,
> 4.1.1 and 4.0.2 docs) when the feature set has not changed within each=20
> of these.  I understand that the docs are built as part of the build=20
> and release process but why does that have to impact the rate at which=20
> the primary doc site is updated.  Can't the patch releases simply=20
> update the release notes?  Personally I think there should be a single=20
> 4.x version of the docs (I would be ok with a 4.0, 4.1 and 4.2=20
> versions too if major features are going to be added to them).  Maybe=20
> the doc site should have wiki like capabilities so that it can be more ea=
sily maintained.
>
> ok, I am done ranting...