Jessica, I think you misinterpreted me (which might be my fault). IMO, we absolutely need the documentation to be posted to the site as part of the rollout of 4.0.0-incubating. In fact, I started a thread about this previously [1]. This includes most of the issues that David mentioned below.
The question was if we were considering doc finalization AND merge into the 4.0 branch as a gating step prior to initiating our first vote. At this point, we've updated the branch with the latest, and the real point is that we're not going to deal with a doc bug that has not been fixed in the 4.0 branch as a blocker issue. Again, we DID want to get the docs done (hence my email on the topic) in time for any actual release announcement. We also wanted to get other website related items completed (cloudstack.org redirect, some content migration, etc...). [1] - http://markmail.org/thread/xvxt66owat5fpq5a On Tue, Oct 16, 2012 at 5:32 PM, David Nalley <da...@gnsa.us> wrote: > On Tue, Oct 16, 2012 at 3:50 PM, Jessica Tomechak > <jessica.tomec...@gmail.com> wrote: >> Just checking up on the issue linked below, "post docs to new doc website," >> and I notice it's stalled. Comments from Noah and Chip are to the effect >> "this can wait until after we get the software out." I'd just like to go on >> record that I think it would be very helpful to users if we can get these >> docs onto the website before 4.0. David N. promised that posting them would >> be a trivial process, so it shouldn't cost anyone too much effort. As far >> as I know, there are plenty of docs built and ready to post, especially if >> we build the version that's checked in to master (lots of nice changes >> after code freeze). >> >> If anyone can chime in with further thoughts, status, or why this can't be >> done, I'd appreciate it very much. >> >> https://issues.apache.org/jira/browse/CLOUDSTACK-246 > > > It is comparatively trivial to publish them - but I haven't as of yet > as fwiu there are still a number of bugs dealing with material > inaccuracies that means that adhering to the docs results in an > inability to get a working CS instance, or even an install. > > Here are some of the issues: > https://issues.apache.org/jira/browse/CLOUDSTACK-344 > https://issues.apache.org/jira/browse/CLOUDSTACK-345 > https://issues.apache.org/jira/browse/CLOUDSTACK-303 > https://issues.apache.org/jira/browse/CLOUDSTACK-134 > > Additionally there are a number of tasks still listed as not done > (completion of the installation guide) > https://issues.apache.org/jira/browse/CLOUDSTACK-4 > https://issues.apache.org/jira/browse/CLOUDSTACK-3 > > > Additionally as Chip pointed out, the installation instructions that > are provided don't resemble installation for anything other than the > developer builds from Jenkins. Wido has agreed to host RPM and DEB > repos, but the project isn't providing anything other than a source > release - and nowhere in either of those is the install.sh > installation method, which is what is documented in the install guide > - so it's confusing at best - and not something that someone can > currently follow. > > That said - if you'll let me know when you consider the docs done, > I'll be happy to publish those (or any other committer can in my place > as well) > > --David >
