Thoughts inline. Jeroen Ruigrok van der Werven wrote: > Given how Christian is coordinating 0.11's release now can we already discuss > the focus for 0.12 a bit? > > What I see on the roadmap seems a bit excessive in terms of planning a new > release (notes inline are mine, comments from others very much welcomed to get > an idea of the scope): > > * Enhanced underlying data model (GenericTrac) > -INT_MAX, not in 0.12 or ever until someone convinces me this is possible while not making things far too complex. > * Basic support for multiple projects (TracMultipleProjects/SingleEnvironment) > -1. I think we should come up with some recipes to handle this better, maybe adding a custom "project" field and some example reports. Full support is going to need more time than 0.12 should take. > * Vastly improved versioncontrol subsystem (see VcRefactoring) > +0 don't know what needs doing. > * Wiki Engine refactoring (WikiEngine) > -0 if it is ready in time, sure. Don't think we should delay for it though. > * Better user/session system > o Optional form-based login > -1, AccountManager does a good job of this already. > o Pluggable user-directory provider (#2456) > +0. Nice to have, shouldn't block. > o Nicer CC-list / "ticket monitoring" (#1459) > -1. Too many possible permutation of this I think. I would rather see it handled by plugins for a while, if it becomes clear that one approach is liked much more, then discuss integration. > * Improved notification architecture (TracDev/Proposals/Journaling, #1890) > +1. This whole system needs to be revamped. > * Improved ticket query system (so that it can be used instead of SQL reports > system in 99% of the use cases) > -1. I am all for adding a bit more (like support for OR), but I would rather keep queries simple and move reports into an external plugin to be installed if the users need more control. > * Improved API for request handlers (see sandbox/controller and the newer > VcRefactoring/Controller) > -0 unfamiliar with these branches. Doesn't sound like it should be a blocker. > * Internationalization > +10. I think this will be a good flagship feature for 0.12, and much work has already been done. > Most of the internationalization framework is already in place in the i18n > sandbox and kept up to date with trunk. I'm working on setting up something > like Pootle locally to get an idea of the current translation coverage. > > * Better help/documentation system (#2656) > -0. I still don't see why people dislike this so much. Namespace-ish support for the wiki seems like a good solution if someone wants to find a nice way to do it.
--Noah
signature.asc
Description: OpenPGP digital signature
