Matt Good wrote: > mb wrote: >> we would like to use trac as a high level merge tracking tool. For this >> to work we need the possibility to define a different workflow. >> >> As I understand it, the code in the workflow branch will do just that. > > Not at this time. Alec deleted the old branch since major changes in > the trunk made it more difficult to merge those changes into the branch > than to start fresh and reimplement the changes on top of the current > trunk. Most of the changes have not yet been added back to the new > branch, so it's not very useful at this time. You can go back and > check out the earlier branch prior to its deletion, but of course the > APIs are likely to change before it's completed.
We used to use the old workflow branch here for a project we are working on as a joint venture with another company. The old workflow was not able to do all that we wanted, so we have since implemented our desired workflow a set of quick and dirty edits to the trunk. The changes can be seen here: http://www.object-craft.com.au/~djc/trac0.11dev.patch Note that there are a number of whitespace cleanups due to us using emacs and doing M-x whitespace-cleanup. Note also that we made it possible to change the owner of a ticket at any time without changing the state of the ticket. We have a fairly complex workflow because planning happens via a steering committee made up of people from both organisations and while we do the development the final testing and ticket closing is done by the other organisation. I have copied part of the wiki page that describes our ticket workflow to here: http://www.object-craft.com.au/~djc/workflow.html Due to the to-fro process that happens between us and the other organisation we need a little more detail in the milestone view than simply closed/open. We changed the roadmap progress bar to show summaries related to the various roles that people take in the project. An edited example is shown here: http://www.object-craft.com.au/~djc/release-1.6.13.html One advantage to the granular workflow implementation is that the management can get a very good overview of the progress of the release cycle from the milestone. For example, it is clear from the progress bar which organisation has the most outstanding work for a particular release cycle. - Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
