Have to differ a bit here. It is VERY NICE to have docs which match the installed system… The latest and greatest is fine, but is often not what is installed. If I do an SVN update, then both are updated together.
Agree that it is a nightmare to keep things up to date in general... Warren On 2012-08-28, at 10:22 AM, Christopher Brooks wrote: We can do this, but then fixing errors in the docs becomes a pain. I like having them on the web so they can be consulted at any time, and we can fix errors in docs that might occur. Chris On Tue, 28 Aug 2012 18:21:56 +0200 Ruediger Rolf <[email protected]<mailto:[email protected]>> wrote: Why don't we bundle a frozen version of the release docs with the release itself in the SVN? So adopters can always can consult their checked out code for details on their release? Rüdiger Am 28.08.2012 18:15, schrieb Christopher Brooks: Michelle, Also, seeing as we're getting into details, we should probably take this over to [email protected]<mailto:[email protected]>. Regards, Chris On Tue, 28 Aug 2012 10:14:36 -0600 Christopher Brooks <[email protected]<mailto:[email protected]>> wrote: Hi Michelle, The insanity that the page title has to be unique is an unfortunate design decision on their part. Is there a better tool for our job of release notes? OK, I guess I didn't realize the need to have separate 1.2 install and configure docs. With that in mind, and looking at the problem of cloning trees, here's an entirely different alternative I've seen other projects using Confluence do it this way, but not sure if it's really a good or bad approach. The idea is that each set of release docs is it's own wiki space. Then the page titles and links don't need to change. You can clone an entire space very easily, then just update it. So install and configure trunk would be it's own space that you just clone with each release. This sounds good to me, but will it get unwieldy to handle dozens of wiki spaces? I like that you could then do something like MH1.2 as the space name. I imagine googling to find the current release might be a bit of a pain, as google might send you to 1.1, or 1.2, or 1.3...so we would have to think about labelling spaces clearly. But it sounds like this would make the release process easier. How would we deal with navigation in the buttons on the left? Chris -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected]<mailto:[email protected]> http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________ _____________________________________ Warren Long Senior Instructional Support Specialist Information and Communications Technology Email: [email protected]<mailto:[email protected]> Ph: (306) 966-5426 <http://www.usask.ca/> [cid:[email protected]]
<<inline: image001.png>>
<<inline: image002.png>>
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
