Mark,

Looks good!

The only thing I noticed is that I wanted to see them in *reverse order* 
(i.e. the latest versions at the top, rather than the bottom).  That 
makes it easier to find the most recent upgrade instructions (rather 
than having to scroll to the bottom of the list).  So, I just went in 
and reordered them.

On 11/3/2011 11:14 AM, Mark H. Wood wrote:
> We might want to leave the section on upgrading to the current release
> in the main Upgrading page and move it to its own child page when the
> next release's documentation is being initialized.  But I did it the
> way I said I would, for now.

I don't mind each being on a subpage to be honest. So, I think it looks 
good for now.

> One thing I didn't think of:  can a page have children which are in
> another space?  If not, then we need to copy the child pages over to
> the new DSDOCn.n space when we start a new version.  Ugh.

A page cannot have a child in another space (though it could technically 
link to a page in another space).  But, in any case, that's no big deal. 
When we do our next version of docs, we always will need to copy all the 
old docs over to a new DSDOCxx space.

So, for example, after 1.8 is released, we will need to eventually copy 
*all* the pages from DSDOC18 to a new space called DSDOCxx -- where "xx" 
is the next major version after 1.8.x.

- Tim

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to