On Jul 23, 5:07 pm, Christian Boos <[email protected]> wrote: > Hello, > > Now that 0.11.5 is out, I'd like to share my views concerning the next > releases. > > First, let's see where we stand with respect to opened tickets (1): > - 43 untriaged tickets -- not that bad > - 18 tickets for which we're waiting for feedback -- good! > - 913 valid tickets to work on... -- hm... > > Looking at the tickets by milestone, we have the current dispatching of > opened tickets (2): > > || Milestone || Enhancements || Defects || > || 0.11.6 || 4 || 32 || > || 0.12 || 71 || 55 || > || 0.12.1 || 22 || 88 || > || 0.13 || 207 || 91 || > || 1.0 || 85 || 39 || > || 2.0 || 92 || 14 || > || experimental || 11 || 0 || > || not applicable || 20 || 41 || > > I think we have too many opened tickets for the next versions 0.11.6 and > 0.12. > Reducing the number of tickets is important in order to be able to get a > release out. As usual, this doesn't mean that tickets which are not (or > no longer) scheduled for these releases can't be finished earlier if > someone is willing to work on them, but at least having a low count help > us to visualize what we'd really like to see implemented next. > > For the 0.11-stable release line, I think we should really start > freezing it now, only considering serious bug fixes and eventually > performance tweaks. On my side, I'd like to fix #8459 ("svn:mergeinfo > performance") and eventually #8349 ("Older Revisions link with revision > list is wrong" - also related to svn:mergeinfo). > There's also #8443 that we discussed earlier ("postgres and IDLE in > transaction status"), most of the rest should probably be moved to 0.12.1. > > For 0.12, we should also consider moving a good deal of tickets to > 0.12.1 (defects) or even 0.13 (enhancements). > > The list of tickets and tasks I'd really like to get done for 0.12 is > there: > http://trac.edgewall.org/wiki/TracDev/ToDo#Release0.12 > I'd like to make the list of 0.12 tickets match the above. > Even as a shortlist, this still represents quite a lot of work, I'm > afraid ;-) > > Other developers are welcomed to list their favorite items as well, > either in the TracDev/ToDo page or in the tickets. Please understand > that those places are intended to be used as a way to coordinate actual > work, so if you simply want to give your opinion on what should be done, > the mailing list is enough. > > The main idea here is that by doing less work on 0.11-stable, we can get > trunk a bit more active. Also, by making the list of 0.12 tickets > smaller, we can make this release happen sooner and have a better > visibility of the things left to be done. > > Let me know what you think!
looking at the huge list of closed tickets for 0.12 (http:// trac.edgewall.org/query? status=closed&group=resolution&milestone=0.12), including very nice features like autoquery (http://trac.edgewall.org/ticket/7562) which is now implemented for nearly a year i wonder what prevents releasing 0.12 now ? the milestone was due two weeks ago :) rupert. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
