On 5/6/2010 2:24 AM, Olemis Lang wrote:
... Ok , so it's possible to start a 0.12 branch and implement this kind of things in there (for 0.12). However it would be very nice if Trac Team could backport repos hooks to 0.11.
... which makes me think we probably have some communication issues between the Trac dev team and the Trac plugin developers.
- 0.11.x is frozen, except if critical security issues are discovered (last release will be 0.11.7.1 at the end of this month)
- 0.12 is being finalized, which means we might consider some small last minute adjustments but other than that, it's "done"
- 0.13 development will begin soon, we're eager to get *more* participation and feedback to the development discussions, and in particular, any suggestions you could have concerning changes to IRepositoryChangeListener can at best only target that release...
And it's not that we didn't try to get some involvement from the community in the past 2 years, when we developed the multiple repository support and even more specifically the IRepositoryChangeListener interface. Search for IRepositoryChangeListener in the Trac-dev google groups, you'll find lots of discussions.
So we're quite open to suggestions, but except when it's about fixing a really serious flaw or some security issue, these things can only concern *trunk* or feature branches (like sandbox/multirepos was), not the stable branch, and even less the previous stable branch.
Now we can also try to make preview releases more often (earlier betas? alphas even?), so that the new features and interfaces could catch the attention earlier. What is sure is that long release cycles we had for 0.11 and 0.12 are not really optimal, and we'll try to shorten that for the next releases (targeting 0.13 by end of this year), while trying to keep the changes as incremental and as less disrupting as we can.
Doing so the plugin could focus on providing those aspects not covered by mainstream hooks implementation . E.g. for some reason both approaches are different (especially interfaces ;o) so it would be nice to make both solutions more interoperable so that hook actions (components) may be written once and used with both Trac 0.11 and 0.12 . Today that's not possible 'cause they are substantially different, different imports, ...
I'd say write an adapter, i.e. one component forwarding the 0.12 IRepositoryChangeListener events to the components implementing your interfaces?
-- Christian -- 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.
