Hi, As some of you may have noticed, the Milestone page for 0.11.5 says "06/23/09", i.e. tomorrow. That timing was based on a 3 month interval between point releases, when we decided to go for a time-based release schedule. The actual interval between 0.11.3 and 0.11.4 was a bit shorter, so this gave us more time for 0.11.5. But now, here we are.
This release is quite interesting, there are quite a number of new features along the way: - better svn support: support for Subversion 1.6, a memory leak fix, and more - usability improvements: icons for attachment links for direct download, provide feedback notices after POSTs operations - new --http11 option for HTTP/1.1 support in tracd; also a few missing Content-Length response headers were added - new "[mimeview] treat_as_binary" setting - support for automatic backups of Trac database during upgrade, beyond sqlite - test infrastructure improvements (rework-testing, with support for alternate database backends) See http://trac.edgewall.org/query?status=closed&group=component&order=priority&milestone=0.11.5 for more. Part of the "better svn support", we will also shortly add support for improved display of the 1.5 svn:mergeinfo property (#7715) and support for the 1.5 style of svn:externals (#7687). There are also a number of tickets with patches that should still go in, for fixing small issues (e.g. #8358, #8283, #8378, this kind). This is all well and good, with a significant number of people having contributed various patches. Thanks! However ... - We're still pretty clueless about the often reported major performance regression with Trac and Apache (#7490). The last hint to date leads to mod_deflate... Could that be related to the Content-Length response header not being set in some cases, and mod_deflate having issues with that? If this is the case, then 0.11.5 should fix it (the #8020 related fixes on the Content-Length header). - There are still a number of svn authz issues remaining opened (#4503, #5097, #5640, #8289) - Certainly a good fraction of the remaining 32 opened tickets will need to be moved to a later milestone I don't think the above points should prevent us from releasing 0.11.5, but is there anything like a show-stopper that I missed? Now for the next steps, I think the tasks already mentioned above (#7715, #7687, the other smaller tickets with a patch) can be finalized this week. Then an upgrade of t.e.o could be done this week-end and a "freeze" and testing period of one week could follow, as we did with quite some success with 0.11.4(rc1,rc2), to avoid the usual Python 2.3 breakage ;-) I won't be available during the first 3 weeks of July, but I'll try to make 0.11.5 ready for the freeze period, until then. Besides, there are quite a lot of tickets waiting on 0.11.6. Should I do the usual, first move the 0.11.6 tickets to 0.11.7 and move the unfinished 0.11.5 tickets to 0.11.6? Or is it time to consider 0.11.5 as one of the last 0.11 releases and start focus on 0.12? (there will be probably a 0.11.6, but do we really want a 0.11.7?). We could therefore move the current 0.11.6 tickets to 0.12.1, as the plate is already full for 0.12 proper. -- Christian PS: mod_wsgi 3.0 reached rc3 today, so it would be nice if somebody could check if it is working fine with the latest 0.11-stable; same goes for Subversion 1.6.3, which is now in pre-release --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
