On Sat, Apr 22, 2006 at 02:59:16PM +0300, Dan Armak wrote: > That sounds good. So I'll write a plugin for the workflow branch's new > extension points, and will modify /query to be extensible as well.
That sounds like an excellent idea. I've been loath to touch the query code, as it looks like it's going to be quite finicky to plug the ITicketField*Provider interface into it, but if you're going to modify the UI it will motivate me to get off my arse and do something :) Perhaps the query module could use an extension point for customising the layout? I'd be particularly happy to get some more testing of the workflow architecture to see what kind of limitations you come up against as it's difficult to foresee what kind of capabilities developers will want in an API. > Until now we've used only released Trac versions in our local install. I'm > willing to work with the workflow branch and later with 0.12dev since you > tell me that workflow /will/ be merged in the forseeable future. Since I > haven't worked with trunk or any branches beforehand - what's their usual > state in terms of regressions and of forward-porting bugfixes? For instance, > 0.9.4 included many small bugfixes, are they also in the workflow branch? 0.9.x and trunk (to be 0.10) diverged some time ago. I keep the workflow branch synced with trunk quite regularly. The change log is linked off the WorkFlow page if you want to check it out. Alec -- Evolution: Taking care of those too stupid to take care of themselves. _______________________________________________ Trac-dev mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac-dev
