Leonardo Santagada wrote:
> 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?
>   

That port was proposed several times, but it's still not obvious yet if 
this will bring any improvement to the current situation. It's a lot of 
work to do the conversion. So this is a kind of chicken-egg situation: 
it's not really possible to commit ourselves to do the switch without 
knowing more about the impact it would have, it's hard for someone to 
invest time on this knowing that all that work can eventually be thrown 
away...

Put it differently: what do you expect from this switch?

> And what about account manager/ldap support?
>   

John started an integration effort, the last changeset says:

  Initial merge working. Removal of registration and email verification 
needed. Lots of other cleanup needed

So I guess that's a start ;-)
See http://trac.edgewall.org/log/sandbox/accountmanager

> 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).
>   

#2086 is certainly one of the most anticipated feature, it's progressing 
well, though we're not there yet. Testing and feedback welcomed ;-)
About the cosmetic changes, they count as real tickets as well. We're 
definitely in need for some CSS expertise and there are lots of 
usability and layout tickets awaiting contributors, don't hesitate to 
help there as well.

-- Christian



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to