Hello, As a short follow-up to the mail of yesterday about the release schedule for 0.12, I'd like to propose that we cut a 0.11.6 release soon. There are many good reasons for this: - we're late - there's a bunch of good stuff in 0.11.6dev (lots of bug fixes, several performance improvements) [1] - having this behind us will make it easier to fully focus on 0.12
The only downside is that if we release 0.11.6 now, a bunch of important issues will be left opened. But as there's no clear action to take for solving those tickets, postponing the release for an indeterminate period of time doesn't make much sense and prevents the good stuff to be delivered to the users. For example, there's the somewhat hard to reproduce #7785 issue, there are still performance issues that are not fully understood in some setups, all things that could possibly warrant a new release once they get fixed. That's why I've moved them to 0.11.7 for now [2], but depending on the timing they will eventually be done for a 0.12.x release in the end (much like 0.10.6dev never got released). So this evening I went through the remaining tickets with Remy, and we think we can prepare a release candidate this week-end, with the usual testing period of one week, next week. Testers, get ready ;-) Tim, wake up the build bots! -- Christian [1] - http://trac.edgewall.org/query?status=closed&milestone=0.11.6 [2] - http://trac.edgewall.org/query?status=!closed&milestone=0.11.7 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
