The page on upgrading DSpace is huge, unwieldy and repetitive, and it only gets more so with time. Should we not split it up by versions? That is: make the "upgrading" page just some general remarks and a table of links to individual documents for specific upgrades (1.0.1->1.1 and so forth).
We might put all the point releases within a single minor release (1.7, 1.7.1, 1.7.2) on a single page, or not. I tend to think that we should just go with simple and put each upgrade on its own page, even if some of those pages would be quite short. An added benefit is that we don't wind up copying a big wad of unchanging advice over and over again as we cut versions of the documentation for succeeding releases. Only the link page has to be carried forward. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgptIorHNlNMh.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
