on Fri Nov 23 2007, Jani Tiainen <redetin-AT-gmail.com> wrote:
>>> * Basic support for multiple projects (TracMultipleProjects/ >>> SingleEnvironment) >> >> -1. Multiple project support has been on the list for Trac2 since day >> one. We should try to get the 1.0 line in solid shape sooner rather >> than later, and use that as a basis for moving towards multiple >> projects. Not move multi-project to 0.x because we can't even get 1.x >> shipped. > > I think it's ticket #130 in t.e.o and last time I checked it was still > on list for 1.0 not for 2.0. I might be wrong though. > > This is two sided thing. It has very high demand and thus people are > finding a ways to overcome this - even plugins. It's a very important feature, I agree. But I think the best thing you can do in the near term is to make the Trac framework incrementally more friendly to such solutions. > There lies danger that someone succeeds to make widely accepted > solution by community. I don't understand why that's viewed as a bad thing. If it happens, you will have everything you need to know how to handle the problem in the Trac core, and to improve on the accepted solution in all the ways that only a core solution can. In the C++ standardization world we aim (though we sometimes fail) to "standardize existing practice," with the goal that what goes in the standard is proven to be conceptually accessible with useful semantics. Seems like a good idea to take advantage of such an opportunity in Trac when it comes along. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
