Christopher Lenz wrote: > 1) Too many changes with too much impact Agreed. Hopefully the development policy we discussed earlier on trac- dev in combination with more focus "release early release often" will help us avoid similar problems in the future.
> 2) Too many API changes without much benefit > 3) Added bloat This one is a bit tricky, we have for a while now been spoiled by an excellent component system allowing Trac to be extended and customized in many different ways. So now most of our users expect the "Trac platform" to be usable for almost any task just by writing a plugin or two. I think in order to keep being able to call Trac a "minimalistic approach" we need not only to think twice about adding new concrete features but also new apis and configuration options. A too complex api and too many config options is also bloat. > What do I think can be done? Well, first I think we need to realize > that 0.11 is further off than some had thought. We need to organize > around fixing the biggest problems, and for the future we need to > figure out ways to avoid such situations and "stay on Trac". Agreed. Even though from a user's point of view trunk might be usable enough for at least a beta release already there are a lot of things we really need to sort out first (both in the code itself and the project) before 0.11 should be released. Cheers, Jonas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
