On Jul 23, 2009, at 12:07 PM, Christian Boos wrote: > 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!
How can I help with the SQLAlchemy port? Is it scheduled for any particular Trac version or even been discussed about including it in trunk? And what about account manager/ldap support? Those are to me the two things that bug me about trac (besides multiple repos that are being worked on and some cosmetic changes regarding the UI). -- Leonardo Santagada santagada at gmail.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
