Mark, This would be fine by me. The only reason this hasn't been done yet is that no one has had time to do it :) I'm all in favor of splitting up large wiki pages into a series of smaller child pages -- so, the upgrade instructions would make perfect sense to split up.
So, if you have time to do this now, feel free (just probably should get it done *before* end of day tomorrow, Thurs, at the latest). If you don't have time, we can do this immediately after 1.8.0 is released. - Tim On Wednesday, November 02, 2011 2:50:40 PM, Mark H. Wood wrote: > 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. > > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
