Now you are getting into how to do this which I intended to carry on in another thread. Yes, we can, but we need to follow the principle of replacing the pages that need update faithfully. So, at the start, the top level is different and everything else is the same. Over time, the specific documentation pages would get replaced (not updated) with the new version for that specific release. At the end of each release, some pages remain the same and some will be updated for the current release. We also need to make sure the subsequent release documentation is built on top of the latest one.
On Wed, Jan 7, 2009 at 2:33 PM, Raymond Feng <[email protected]> wrote: > Cannot we just have separate top-level pages to contain the document > hierarchy for different releases instead of multiple wiki spaces? For > example, we can have sca-java-1.x and sca-java-2.x. > > Thanks, > Raymond > -------------------------------------------------- > From: "Luciano Resende" <[email protected]> > Sent: Wednesday, January 07, 2009 2:03 PM > To: <[email protected]> > Subject: Re: Versioned Documentation by SCA Java Releases > > > On Wed, Jan 7, 2009 at 9:05 PM, haleh mahbod <[email protected]> wrote: >>> This means a few things: >>> >>> - We need to have a wiki space per release. Let's talk about how >>> to do this in another thread if there is agreement to go ahead. >>> >>> >> Trying to understand your definition for "one wiki space per release". >> So, in the scenario where we would have 1.4, 1.4.1, 1.5 and 2.0 these >> means 3 documentation wikis (1.4, 1.5 and 2.0) ? >> >> Another option would be to have a 1.x and 2.x and each release ship a >> snapshot of the wiki as it's documentation, this way we would probably >> reduce the admin and documentation work needed. But we would need to >> investigate how we would "ship the snapshot" of the documentation. >> >> >> -- >> Luciano Resende >> Apache Tuscany, Apache PhotArk >> http://people.apache.org/~lresende >> http://lresende.blogspot.com/ >> > >
