> That's ok, because the support in this mailing list and by the authors > is great, but I can hardly imagine to do so for every Trac update. > Perhaps it's better not to rely on plugins...
Plugin/extensions are quite new in Trac world. I guess plugin developers are encouraged to follow the same release stream on trac-hacks than the Trac development stream (0.9, 0.10 and so on). [being myself a plugin developer, I know I did wrong not following this rule, blame me....] Upgrading from one minor release to another (ex: 0.9.2 -> 0.9.3) should not break up plugin in most of the cases, but if plugins are designed to work against the Trac trunk, there cannot be any warranty about the external APIs. I guess it's all about compromises: features+tweaking vs. stability ;-) Anyway, if you fixed up the issue with the latest trunk, please post the diff on the ML. Thanks Cheers, Manu _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
