> Some time ago I've updated the ApiChanges page for 1.1.1, proposing a > few changes that I think would be good to undertake early in the 1.1.x > development cycle. > > http://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1.1 > > Among these, I suggest that we now only target Python 2.6 and 2.7, > and I highlight there a few possible benefits of dropping 2.5 support. > Another "benefit" would be to get the syntax closer to Python 3 (3.3 and > beyond, see #10083). > > So for those who have not yet reviewed the proposed changes, this is the > occasion to do so and give me some feedback about it ;-)
Date type custom fields would be nice. I worry how I'm going to support multiple version of Trac in my plugins since I can't figure out how to branch in svn at T-H.o, let alone make it talk nice with my local git repositories. -- 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.
