On Saturday, January 9, 2016 at 12:07:43 PM UTC-8, Tim Graham wrote: > > Sounds good to me. You wouldn't intentionally break support in already > released versions of Trac, just no longer fix new issues, correct? >
Thanks for the feedback. I'm just proposing to no longer fix new issues for IE < 11. > As a data point, Django 1.9 (released Dec 1, 2015) switched to jQuery 2.x > which has the same API as jQuery 1.x, but does not support Internet > Explorer 6, 7, or 8, allowing for better performance and a smaller file > size. > > By the way, is this statement on (1) that you linked correct? "These notes > reflect the current status for 1.3.1 > <http://trac.edgewall.org/milestone/1.3.1>, in trunk > <http://trac.edgewall.org/browser/trunk>" That seems to suggest that > trunk is open for changes for the 1.3.x series, but as far as I know, it's > still 1.1.x. Maybe I misinterpreted... I would still like to help out with > Python 3 support when the time is right. > The trunk is still 1.2dev. I'm working on wrapping up 1.2 development and look forward to working with you on adding Python 3 support. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
