Re: Proposal to manage documentation similar to (or along with) core software.
Mikko Ohtamaa <mikko+plone-75aZqqp77KCaMPzRcYMCawC/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
aclark wrote: > > Right, but up to date docs != versioning. We have not *versioned* and > *released* docs to date. That needs to start happening now with Plone 4 > IMO, > so that by the time Plone 5 rolls around we can look back and say > "Ahhhh, these are the docs we shipped with Plone 4". > This is very good idea. However I think the train for Plone 4 has already left and it would be more realistic to target with versioned docs to Plone 5. E.g. * Create a place for Plone 5 documentation when the development process is kicked off * Populate this place from docs from plone.org doc area * Make sure every doc is updated regarding Plone 5 - e.g. a workflow with "Plone 5 approved" switch * Release ... or ... * Have a collection, or collection of collections, which will pick up Plone 5 docs from docarea mass Too complex? ----- Mikko Ohtamaa mFabrik - Freedom Delivered. Web site - http://mfabrik.com Mobile site - http://mfabrik.mobi Blog - http://blog.mfabrik.com -- View this message in context: http://n2.nabble.com/Proposal-to-manage-documentation-similar-to-or-along-with-core-software-tp4899546p4924106.html Sent from the Documentation Team mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev