In order to realize the compelixity of the trac development, the team should start to decouple the Core functionality.
This will result in an (incomplete) web application framework "core", which relies on the (incomplete) genshi template system. All this is essentially independent of the (incomplete) application "trac". [btw: A possible name for this framework could become "cart" - the reversed "trac"] As a first step, an additional folder "trac/core" could be created. The relevant code is moved to this folder, after refactoring the code in small incremental steps during the main development. A possible start would be right after setuptools is merged to 0.11dev. - Some things subjecting the active development: What is the status of the setuptools migration? Possibly the team should collectively focus to solve all issues to finalize this step. I've noticed a fresh start of the sqlalchemy migration. Possibly this should happen unit-wise. E.g. if the wiki is migrated to sqlalchemy, it should be tested and merged to trunk. Then e.g. another system should be migrated, tested and the merged. I am not sure if all those is applicable,. . -- http://dev.lazaridis.com/base/wiki/WorkingPlans --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
