Hi Robert: On Thu, Aug 9, 2012 at 9:31 AM, Soulliere, Robert <robert.soulli...@mohawkcollege.ca> wrote: > Hi All, > > I set up Documentation processing for Evergreen 2.3. This is in “Alpha mode” > and available for review. > > It is available in the “Under Development” section of our documentation > launch page: > > http://docs.evergreen-ils.org/ > > > I also added an outline page for folks working on content to update progress > on chapters and sections: > > http://www.open-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.3:outline > > You might notice a number of “Can this be pulled from 2.2 content?” notes in > red. > > The content for those chapters are already in 2.2 and are easy to pull into > 2.3. All I need is for content authors or developers who are familiar with > the content or development of the features in these chapter to indicate “yes” > using the outline or the DIG list or launchpad. Then, I can pull it in.
I'm sorry, but I don't think this is a sustainable model. I think we have to assume that all of the 2.2 content should be pulled into 2.3, and then deal with the exceptions as they arise. Beta-testers can open bugs against the documentation if they find discrepancies between what is documented and what they see in the beta release, but they can't do that if there's no content to look at. Perhaps as part of the Launchpad "pullrequest" and the review process, we could start flagging areas of the documentation that need to be changed as new features are added, or as old features are deprecated?
