Hi See http://trac.edgewall.org
For the creation of components you can use webadmin ( http://trac.edgewall.org/wiki/WebAdmin). And for workflow start by reading this - http://trac.edgewall.org/wiki/TracWorkflow Cheers / Erik On Nov 28, 2007 3:23 PM, joluinfante <[EMAIL PROTECTED]> wrote: > > Ok, Daniel. Thanks for your answers. > I have more questions... > > * Where I can learn about "create components". Can a component be > created by a gui interface or, I need update parameters files with vi? > * Where I can learn about "default workflow"? > * You say "in the new version, the workflow will can be customized". > I'd like to see, in the customization, the posibility of execute a few > scripts to do the changes in the svn. Is It in the route map? I need > use the bug tracking system to complement the change management of > sources (the source in the svn db). > * Do you speak spanish (my english is bad, you can see). > > TIA > jorge infante > sysadmin > rosario - santa fe - argentina > > On 27 nov, 10:16, dserodio <[EMAIL PROTECTED]> wrote: > > On Nov 26, 7:30 pm, joluinfante <[EMAIL PROTECTED]> wrote: > > > > > 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 afirstcontact with the product. > > > > Helix? What's that and how does it relate to Trac? > > > > > 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? > > > > Trac provides a "read-only" interface of the Subversion repository, so > > you'll need to import your existing sources using "svn import" or > > similar. > > > > > * 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). > > > > If your applications are composed of several "projects", then it > > sounds good, an environment for each application and a component for > > each project. > > > > > * 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? > > > > With the current released version (0.10.4), you cannot customize the > > default workflow, which you can see > herehttp://trac.edgewall.org/wiki/TracTickets > > > > For the next release (0.11) it'll be possible to customize the > > workflow as you like, search the Trac wiki for details. > > > > Hope this helps, > > Daniel Serodio > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
