Hi all,

this is my first post.  After doing a search, I see that in the past a
few people have expressed a desire/need to have the wiki version
controlled, or parts of it, for different reasons.  I too am
interested in this, and was wanting some opinions on what would be the
best approach to something like this.  Particularly I am thinking in
the context of using the Wiki to hold requirements/design/test plan
documents, which would need version control, along with tickets to
things like reviews and approvals. (if not tickets, some external link
is OK too)

My initial thought here, is that it's something that should be done
outside the Trac system, and Trac extended in some way to pick up the
changes automatically, or by way of a 'update' process to import
changes.  This way, I could manage my documents outside of Trac,
export them to some useful format, say csv, xml, plain text, etc.,
version control that document, then in the wiki, have the changes
reflected somehow.  For me, this is likely the best route, since,
these documents have a multitude of sources, DOORS, Word, Excel, etc.

That said, how would one go about something like this?  Maybe a SVN
post commit hook that forces Trac to update?  I'd still want the
difference in  the wiki pages to show up in the Trac timeline, can
this be done?  Etc.

Basically, I'd like this controlled documents to be available to view
in the wiki, plus if possible had trac features associated with part
of them, such as tickets and/or the timeline features.

At any rate, I am interested in hearing feedback

Thanks.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to