osimons wrote: > So, either I can fix this in the plugins - and call various forms > depending on Trac version.
Simpler to maintain and cleaner solution: just make a 0.12 branch for your plugin. That's also simpler for the users. > Or, Trac can be fixed to allow a graceful > migration of this API change supporting both new and old-style > callers. Well, in this case, I think it's better to break the compatibility, as there's no way to get the complete information from the old call. Being backward compatible in this case means support broken link labels (e.g. when the selected language is french, we would have: "Précédent Post", "Suivant Post"). > I'm quite tempted to fix this in Trac and have held out on > comitting the fix for Bitten (http://bitten.edgewall.org/ticket/450) > until I had time to look into the Trac side. Which means I need to get > my 0.12 development setup running again... Which may still take some > time... > > > :::simon > > https://www.coderesort.com > http://www.ohloh.net/accounts/osimons > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
