| | 32 | == Multiple Project Support |
| | 33 | |
| | 34 | There is little doubt this is the [SeaChange/WhatUsersWant#Voteforyourpreferedpluginfunctionalitymost wanted feature] for Trac. |
| | 35 | The ability to create lightweight projects from within the same single environment, to better match complex development environments with new products, plugins or implementations sub-projects appearing and disappearing would quite certainly be appealing to a lot of current and potential users of Trac. Many users are actually more or less forced to switch to alternative solutions more flexible in that aspect (e.g. RedMine). |
| | 36 | |
| | 37 | For a long time, this has been dubbed to be 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. |
| | 38 | |
