New Strategy for release documentation
a.cheetham at utoronto.ca
Thu Jan 15 17:24:36 UTC 2009
On 14-Jan-09, at 12:20 PM, Justin wrote:
> Instead of cloning, or losing the documentation we can link back to
> previous pages.
+1 for a better approach!!
In principle, your suggestion looks great. However, I don't understand
one key part of the implementation:
> Steps at release:
> 1) Ensure the documentation is up-to-date for the current release
> 2) Remove the info box at the top of the page which links back to
> the page for the previous release.
> 3) Save this page, as it will be the documentation for the current
This is the step that confuses me - what does this mean? How do you
'save this page'? Is this some wiki functionality that I'm not aware of?
> 4) Place the info box back and change the link to point at the page
> saved in step 3
Anastasia Cheetham a.cheetham at utoronto.ca
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
More information about the fluid-work