Hi, On Fri, Jul 27, 2012 at 1:44 AM, Joe Schaefer <joe_schae...@yahoo.com> wrote: > I'm sure I speak for Marvin when I say I would love to participate on a task > force dedicated to producing such documentation, but I am also weary about > writing about a whole bunch of hypotheticals that nobody (other than Roy) > has a really good handle on anyway.
That's a key reasons for why I think it would be a good idea for the task force to spend time looking at actual release candidates and helping podlings with the release process. If there's an issue that isn't clearly documented, then fix that, otherwise just point to existing docs on the matter. The existing Incubator release guide [1] is a noble effort, but I think it went wrong in trying to explain everything (even the table of contents is TL;DR, and parts of the page are already outdated) instead of just pointing to more authoritative information under http:://www.apache.org/dev/ and fixing/clarifying that documentation in-place where needed. I'm of course happy for volunteers to contribute in any ways they prefer, but as general guidance I'd be vary about the idea that simply writing more documentation, especially without a firm rooting in concrete problems, will help solve the issue. [1] http://incubator.apache.org/guides/releasemanagement.html BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
