On Wed, Apr 29, 2009 at 7:29 PM, Howard Lewis Ship <hls...@gmail.com> wrote:
> It might be possible for a wiki to operate in the same way ... we > could have a Tapestry 5.1 space and, at the start of 5.2, we could > copy it to form the Tapestry 5.2 space. In this way, > the documentation for prior releases would be accurate (we could even > freeze the space), but would still be open to a community effort to > keep it up to date. That seems to be the way that Atlassian uses Confluence for their own documentation -- they copy the space for new versions. You might still not want a frozen space for released versions -- there's almost always room to improve documentation. Community docs can be of lower quality than "official docs", but it certainly isn't always that way. I'm sure it's a tricky balance. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/
