Trac Sprints

Next Sprint

The next sprint will be at ​PyCon 2008 from Monday, March 17th until Thursday, March 20th. There will be an introductory session on Sunday, March 16th at 4:40pm CDT.

Sprint Ideas

• Work on 0.11 Release - Should have a 0.11b2 by then. +10
• Get sandbox/testing ready to merge
• give evil_twin a brain
• Work on sqlalchemy branch _{(but see caveats belove — cboos)} +1
• Internationalization
• Pluggable user-directory provider

Eli Carter

• Get my "mergebot" stuff on ​t-h.o

John Hampton

• Port ​TracBlogPlugin to 0.11
• Work on Tags based permission policy plugin

---

Notes

SQLAlchemy

I'd hate to see a lot of effort spent on the superficial aspect of the SQLAlchemy port, because that could be eventually wasted if we don't first answer the more fundamental questions. The data model creation part has been done (I think), we know porting the statements is doable (only lots of work) - what we don't know yet is if the benefits brought by SQLAlchemy on the infrastructure outweights the disadvantage of adding yet another required dependency.

So I'd welcome any progress on the SQLAlchemy integration, but it has to address the right questions:

• better pool handling?
• no new / different multithreading issues?
• evaluate the impact of SQLAlchemy on all the open issues for PostgreSQL, SQLite, MySQL i.e. does SQLAlchemy help, make things worse, is indifferent to the issue?

I also wonder whether it would be better to move to Elixir now instead of plain SQLAlchemy. Makes the models much cleaner, IMHO. — djc