Hi, I'm having similar requirements. I'm looking into a XML based storage under source control and then a plugin to grab and format the information from there. Something similar is already done in the TestCaseManagementPlugin [1], but there the information of the stored XML is used for automatic ticket creation and reporting.
I have not yet thought about a linking or automated WIKI page creation from the source, esp. how to distinguish between the different branched versions of the requierements. With the XML information at hand, one could also generate a requirements traceability matrix and a lot of other nice things. But this is only in my head. I have no code to show. The reason for keeping the requirements with the software under source control, is simply that requirements change. Except bug fixing, every version of the software exposes a different set of requirements since every checkin will extend or modify the current set of requirements. Since you can not easily create wiki pages that follow your software versions (e.g. see the discussion about the trac documentation itself) it is necessary to store the information under source control. Best regards Dirk [1] http://trac-hacks.org/wiki/TestCaseManagementPlugin [EMAIL PROTECTED] schrieb: > On Jun 2, 5:02 pm, "Erik Bray" <[EMAIL PROTECTED]> wrote: > >> I don't know about you, but I just keep all my requirements in the >> wiki itself. Usually as a bullet list, so I suppose I can't link to a >> specific requirement. But I can see, "See requirement 123" and link >> to the appropriate page. I'm not saying that necessarily suits your >> needs, but it sounds to me like you're getting over-complicated. >> > > Wish it were that simple. I can't actually put the requirements into > the wiki. I have to export them from a controlled location, this > "solution" I am after is post export. I suppose I could find a way to > export to wiki mark-up. some how. I want the wiki-version of the > requirement to be up to date with the source control version, which is > generated auto-magically by the requirements tools. Seems to me the > pinch point is that export, I should transform to wiki markup at that > point, update/check into source control, and #include it in an > appropriate wiki page. > > I will let you know. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
