On Fri, Mar 09, 2007 at 05:27:51PM -0600, Eli Carter wrote: > Discuss. I'll join in the discussion on Monday.
Caveat lector: I haven't read or tried the code, I'm just reacting to your description of the process. Personally, I'm more and more of the opinion that we should not have the option of configuring workflow via trac.ini. My reasoning is that whatever we provide is either going to be insufficiently flexible for most people, or so complex to use that most people won't bother. Moving on, I think the goal of offering different workflow options in stock trunk would be better served by offering multiple components implement ITicketActionController. These alternate workflows should probably be in the sample-plugins directory as I think we should provide only *one* definitive workflow in Trac core to avoid confusion. Finally, regarding the default workflow for 0.11. I think we should ask whether any changes we make are truly necessary, or just "nice to haves". If they are, we should ensure the new workflow completely encapsulates the previous workflow so that users are not left out in the cold. Another option, if we change the default workflow, is to provide the old workflow as a plugin. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
