about "developer-manual work-in-progress" and release versions
Kurt Bendl <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.documentation |
|---|---|
| Message-ID | <[email protected]> |
Hi folks, First: http://plonemanual.twinapex.fi/ == Awesome! Mikko's comment about some content being "old" and "confusing" is spot-on. Version soup. 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/*"] When a new version rolls out, copy with the previous version (if appropriate), stick it in a new folder, and make changes where appropriate. I believe this approach works more like people think. Well, at least it work more like I think. Disk space is cheap. Let's take advantage of it. :-) Other successful open source projects do this (apache and python come to mind) and it "just works". I believe http://plonemanual.twinapex.fi/ is a perfect candidate for this. Opinions? /me ducks for cover :-) -Kurt On 10/15/2009 08:09 PM, Mikko Ohtamaa wrote: <!-- snip --> > The information is old and partially just confuses the reader. > > The information is superseded by Plone Developer Manual. The link for new > developer-manual work-in-progress version is: > > http://plonemanual.twinapex.fi/ > > This will be migrated to plone.org in some point. The point being, when > there is more than one active maintainer for the documentation, besides me, > and we have necessary PHC infrastructure done. > > -Mikko <!-- /snip --> Kurt -- Kurt Bendl - ITD 4075 Elmwood Ave. Louisville KY 40207 Phone: 720-633-8665 Fax: 888-824-3131 ------------------------------------------------------------------------------ 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