On 01/11/2010, at 10:26 PM, Brian Fox wrote: >> The barrier to collaboration is high here. > > That's all I'm saying. The tools make that partially true but it's not > stopping other projects so it's clearly not the only issue. Maybe no > one really cares about these plugins, and for the ones raised so far, > that's probably the case.
The problem here is the way in which we abuse JIRA (by necessity). A change of source control would make little difference, other than if it were to route around issue tracking which isn't particularly helpful. Some people watch patches on specific subprojects, other subprojects get neglected (perhaps picked up in bursts). Not all such subprojects are retirable. No other project I know of tracks small components in such a way, and we regularly lose sight or timeliness of patches. IMO, we should reconsider our approach, or look again at aggregation, or some way of keeping track of patches across projects. The limiting factor is in time, communicating and testing, not in applying or releasing them. Those parts are about 10% at the start and end. The rest is in the middle, and perhaps the pressure to fix more things while you are there. - Brett -- Brett Porter [email protected] http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
