Hi, forum. I'd like to use svn, for do versioning of the sources, and I'd like manage the workflow (state of changes). For it, I did download helix, to do a first contact with the product. I have a few "applications" (erp, commercial, technical maintenance), with daily changes (new features, bug correction). I need: * put all sources of each application in svn. I can do it with trac? * each application contains several projects, I need to create "a component" for each one. Is it the correct method? I have projects in a lot of languages (oracle forms, delphi, c#, vb6, java). * Create a ticket for the change requirement in a component (an end user can do it), then the boss of developers take the problem, and put it in a tasklist of a developer, then the developer do the change, then the component is ok for test, then the component is validated as ok for the end user, then the end user authorize the move to production environment of the component. Is it this posible with trac? My erp is oracle-financials (a lot of components). My commercial application contains 600 forms and 400 reports. My technical maintenance application is about of 200 jsp's (I can only customize the presentation layer)
Can any person help me with "where I can learn about the trac use in a practical case, like my case"? TIA jorge infante sysadmin rosario - santa fe - argentina --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
