
|
[dokuwiki]
||
[Date Prev]
[07-2007 Date Index]
[Date Next]
||
[Thread Prev]
[07-2007 Thread Index]
[Thread Next]
[dokuwiki] Re: Best practices of multiple documentation releases
- From: Guy Brand <gb@xxxxxxxxxxxxxxxxx>
- To: dokuwiki@xxxxxxxxxxxxx
- Date: Tue, 3 Jul 2007 18:33:32 +0200
On 01 July at 23:58, Pavel Shevaev wrote:
> We have the following schema of large releases: 2007.1, 2007.2, 2007.3
> and so on. Once we make a release we copy the "trunk" directory of
> documentation into new directory called after the release. Once copied
> we apply simple perl one liner which fixes all links for all pages in
> this directory.
>
> Well it works but honestly I'm not sure how good this solution is.
You could also use a wiki farm and store each branch of the doc in a
separated wiki (with shared acl/users of course). There are only a
few changes to get it working: http://wiki.splitbrain.org/wiki:farm
Once a release is made, freeze the doc by creating a new wiki in the
farm and go on working in the trunk/head wiki.
Maybe this could fit until we have a "delegate versioning to a VCS"
plugin or a way to tag versions of pages/namespaces as discussed in
the thread.
--
bug
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist
|

|