On Jun 2, 5:35 pm, [EMAIL PROTECTED] wrote: > 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. I was considering xml as well, with a style sheet. I am exporting from DOORS, if you're familiar with it, great, if not, it's a database for all intents and purposes, with lots of export options, and can be customized. I do like the mime-type idea as well. I still have something nagging at the back of my head(that would be my wife btw) saying this is a database solution. the Data CAN be accessed at the DB level, although its usually easier to just export, the items in the database are versioned as well, so versioning is covered. I wonder if it would be easier to just export to html, and modify the export with the embedded #links....
Anyway, I think I went down my now, seemingly convoluted options because I was considering plain text requirements documents instead. So, I think I have my solution options: - direct DB access seems ideal, but a pain. and it would have to be via a python layer in between, since I think the api is command line only. not sure if there is xml-rpc, will have to look, and still need to render in a friendly format. although, the ability to query etc is a bit sexy. - export to modified html with ref links, automatically commit to subversion (we need to version control released document anyway in some format as a super retentive back up of the already backed up source), and #include the file into a wiki page. then I can actually link to the document, and the ref link. sounds like more work, but probably is actually easiest, and requires no trac plugin creation. - export AS wiki formatted pages, and check into version control. actually, in this case, I could technically NOT version control the wiki content, and export to another format for archiving purposes (say, pdf). and then I could "update" the wiki, which is versioned by trac, and I get change tracking, et al. You realize, I will end up trying them all eventually! Dfjafldajfa it! anyway, thanks all for letting me babble this out on the group, have a cup of coffee on your respective engineering departments! (we have 2 coffee pots: Engineering, and rest of the company) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
