Luciano Resende wrote:
On Wed, Feb 4, 2009 at 7:32 AM, Dan Becker <[email protected]> wrote:
This is a good proposal Luciano. I like the idea of "branching" the docs.
Just as the Sun JDKs provide versioned docs from the 1.0 days to the current
1.6 days, I too would like to see versioned Tuscany docs.
In addition to versioned wiki spaces, we might want to think about versioned
public pages. Right now there is an export plugin that moves the wiki pages
to the external site html pages. Perhaps we need to branch the tuscany web
site so there would be a "latest" html snap shot at
http://tuscany.apache.org and earlier "versioned" html snap shots, perhaps
at http://tuscany.apache.org/1.4, etc.
What problem are you trying to solve here ? Confluence is much like
SVN and provides a change history for each page. Would that be ok for
website ?
I am thinking more along the line of what the user sees for the Tuscany
website after the wikis are exported to the world. Is the user going to
see several site versions, e.g:
http://tuscany.apache.org (latest)
http://tuscany.apache.org/1.5 (previous release)
http://tuscany.apache.org/1.4 (previous release)
Or is the user going to see several article versions on one site?, e.g.:
http://tuscany.apache.org/sca-java-user-guide.html (latest)
http://tuscany.apache.org/sca-java-user-guide-1.5.html (previous version)
http://tuscany.apache.org/sca-java-user-guide-1.4.html (previous version)
Or maybe we have other version publishing ideas in mind. Of the two I
mention here, I prefer the first one.
--
Thanks, Dan Becker
