Question
We are using Twiki to develop software requirements between multiple groups.
For each of our products we have created multiple topics that document the requirements for a specific product.
As our product managers develop these specs, our designers and engineers will review and expand on each topic page with design and functional specifications.
Our problem is that we would like to have the ability to "tag" a specific revision of a Topic to tie it to a release number. That revision may continue to be edited by our engineers while our Product managers continue to edit the latest version, and then have the ability to merge the edits in at a later date after that release has been launched.
We've seen some workflow plugins but those lock the topic page down for approval processes.
We're looking for something that essentially allows us to tag, branch, and merge topic pages.
Environment
--
MikeWu - 16 Jan 2007
Answer
If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.
At this time there is no automated way of tagging, branching and merging of TWiki topic content. This would go against the simplicity of wikis, but in your case it would make sense to have.
As a workaround, for each product release you can create a topic that either links to related topics with relevant version number, or include all related topics with relevant version number.
--
PeterThoeny - 16 Jan 2007
Tagging is pretty easy; branch and merge is not really on the menu.
To tag, just write a script (could be command line or CGI) that gets the
RCS revision numbers of every topic in the database, and stores them to a tag topic. See the documentation on the
rlog
command.
Branch and merge is a PITA in
RCS, and not recommended. If you have some dev resource you may want to look at the Subversive store implementation, which is in the TWiki subversion repository. However TWiki have no built-in support for branch and merge, so the best you could do is to run TWiki over a checkout area.
--
CrawfordCurrie - 21 Feb 2007