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].
Regards,
Chris
On Tue, 28 Aug 2012 10:14:36 -0600
Christopher Brooks <[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
--
________________________________________________
Rüdiger Rolf, M.A.
Universität Osnabrück - Zentrum virtUOS
Heger-Tor-Wall 12, 49069 Osnabrück
Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
E-Mail: [email protected]
Internet: www.virtuos.uni-osnabrueck.de
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
