Re: about "developer-manual work-in-progress" and release versions
Mikko Ohtamaa <mikko+plone-75aZqqp77KCaMPzRcYMCawC/[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Kurt Bendl wrote: > > > I would really like to see documentation separated > by version moving forward, e.g., > ["/docs/3.3/*", "/docs/4.0/*","/docs/4.1/*", "/docs/5.0/*"] > > This would be great. However I don't expect this happen in any time soon. Plone community has its hands full to learn to do development documentation at all. As long as people are not committed to do proper API documentation and as long as the most of the code base consists of old, undocumented, Zope 2 based components, this is just something you can dream on. It is unnecessary difficult for a third party to figure out when a particular function was added or removed unless that is being documented in the code itself. -MIkko -- View this message in context: http://n2.nabble.com/Removing-common-recipes-tp3832795p3837163.html Sent from the Documentation Team mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference