No it wouldn't slow down development, people would just develop on branches at the same speed as they do now. It would just mean that trunk would only get the features when they work, rather than having incomplete and untested code littering it.
Don't knock it, it works for the Linux kernel devs ;)
2010/4/15 Javier Agustìn Fernàndez Arroyo elhoir@gmail.com:
bad one, i guess that would slow down development a lot
On Thu, Apr 15, 2010 at 11:14 AM, Peter Millerchip peter.millerchip@gmail.com wrote:
Yes, I agree too - trunk should ideally not contain non-working code. Maybe non-working drivers belong in a branch until they've been fully tested?
Maybe trunk should be locked to everyone except a "trunk manager" who accepts patches from people, or merges different branches in to trunk. That way trunk can remain stable and lean. Would that be a good idea, or a bad one?