| 41 | | There is little doubt this is the [SeaChange/WhatUsersWant#Voteforyourpreferedpluginfunctionality most wanted feature] for Trac. |
| 42 | | The ability to create lightweight projects from within a single Trac instance, to better match complex development environments where new products, plugins or implementations sub-projects appear and disappear over time would quite certainly be appealing to a lot of current and potential users of Trac. Many users in need of this feature have actually been forced to switch to alternative solutions more flexible in that aspect (e.g. RedMine). |
| 43 | | |
| 44 | | For a long time, this has been thought as a "post-1.0" feature, but instead of waiting for this hypothetical long term achievement, we should actually start to think about getting there incrementally. The MultipleRepositorySupport added in [milestone:0.12] was actually a very important step in this direction, as it already makes it possible for each project to have its specific repository (or set of repositories). See TracDev/Proposals/MultipleProject for some early discussion on this topic. |
| 45 | | |
| 46 | | Like it was the case for the MultipleRepositorySupport, MultipleProjectSupport should have no impact on users who won't use it. |
