On Aug 28, 2013, at 12:11 PM, Ron Wheeler <[email protected]> 
wrote:

> I am hoping that an installation procedure that will not install would be 
> considered a critical/major blocker.
> It stops everyone trying to get started with CloudStack and generates a ton 
> of work in this forum fixing installations that are not working.
> 
> 
> The dev team asked for help, we read the docs, wrote the JIRAs. Some of the 
> fixes for the JIRAs are pretty clear and some require a bit of thought and 
> some restructuring of the docs to get rid of useless commentary or to move 
> stuff from one place to another.
> 
> Someone has to fix the docs or fix the software to match the docs.
> 
> There are probably more bugs in the installation but since I have never been 
> able to find out the exact error or omission that causes the problem, I have 
> not been able to write a JIRA for that.
> I have never been able to get it to install so I can not even suggest how to 
> describe the network setup in a way that makes sense and works.
> 
> The installation needs to be tested by someone who will know that the step is 
> wrong or that some other step needs to be added.
> I am willing to act as a dumb sysadmin beside someone who knows what it is 
> supposed to say but I have written as many JIRAs as I know how, at the moment
> 
> Ron

Ron thanks for that,

I believe that we all recognize that the docs need a lot of work. We as a 
community have discussed breaking out the docs in a separate repository so that 
they can be managed easier and fixes can be made public between releases.

Also while there are clearly dev folks in this community, everyone can help fix 
the docs, by providing JIRA tickets as you have done, or even by submitting 
patches to fix them.

Everyone is doing its best to make CloudStack a great software project. They 
are over 280 clouds in production that we know of, so while the docs are not 
great, a lot of folks manage to get it working.

I am looking at your bugs now, in my spare time, and I will see if I can fix a 
few of them once I put my kids to sleep. If you want you can actually make them 
blocker bugs and join the dev@ list to make your point that they need to be 
fixe before releasing 4.2. 

We would really appreciate the help from anyone on these lists to help file 
bugs and fix them.

thanks,

-Sebastien

> 
> 
> On 28/08/2013 11:59 AM, Conrad Geiger wrote:
>> Blockers are usually the issues that prevent a release.  Other bugs are 
>> often fixed in a point release.  Time based released makes it a little 
>> interesting.
>> 
>> They did recently ask for help on the docs from the community.
>> 
>> 
>> 
>> -------- Original message --------
>> From: Ron Wheeler <[email protected]>
>> Date: 08/28/2013 11:54 AM (GMT-05:00)
>> To: [email protected]
>> Subject: Re: Are we going to see CS 4.2 rc1 out anytime soon?
>> 
>> 
>> I hope that someone on the dev side is checking for outstanding issues
>> before putting it to a vote.
>> There is no point asking us to write JIRA issues if they are not going
>> to be addressed.
>> These documentation problems have been around for a long time without
>> getting fixed and they cause a lot of problems.
>> 
>> Has anyone tested the installation instructions as part of the QA
>> testing process?
>> 
>> Ron
>> 
>> On 28/08/2013 11:35 AM, Conrad Geiger wrote:
>> > They are currently on the third round of voting. Checkout the dev list.
>> >
>> > -----Original Message-----
>> > From: Ron Wheeler [mailto:[email protected]]
>> > Sent: Wednesday, August 28, 2013 11:28 AM
>> > To: [email protected]
>> > Subject: Re: Are we going to see CS 4.2 rc1 out anytime soon?
>> >
>> > On 28/08/2013 10:52 AM, Dean Kamali wrote:
>> >> Hello everyone
>> >>
>> >> going over docs, CS 4.2 rc1 should be released today, just wondering
>> >> if we are going to see it soon.
>> >>
>> >> Thanks
>> >>
>> > Still 10 JIRA issues that I reported, open against installation docs.
>> >
>> >
>> > --
>> > Ron Wheeler
>> > President
>> > Artifact Software Inc
>> > email: [email protected]
>> > skype: ronaldmwheeler
>> > phone: 866-970-2435, ext 102
>> >
>> >
>> >
>> >
>> 
>> 
>> -- 
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: [email protected]
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>> 
>> 
> 
> 
> -- 
> Ron Wheeler
> President
> Artifact Software Inc
> email: [email protected]
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
> 

Reply via email to