But wait with Linux doesn't it work because there's one person ultimately controlling it?<br><br><div class="gmail_quote">On 15 April 2010 10:37, Peter Millerchip <span dir="ltr"><<a href="mailto:peter.millerchip@gmail.com">peter.millerchip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">No it wouldn't slow down development, people would just develop on<br>
branches at the same speed as they do now. It would just mean that<br>
trunk would only get the features when they work, rather than having<br>
incomplete and untested code littering it.<br>
<br>
Don't knock it, it works for the Linux kernel devs ;)<br>
<br>
<br>
2010/4/15 Javier Agustìn Fernàndez Arroyo <<a href="mailto:elhoir@gmail.com">elhoir@gmail.com</a>>:<br>
<div class="im">> bad one, i guess<br>
> that would slow down development a lot<br>
><br>
> On Thu, Apr 15, 2010 at 11:14 AM, Peter Millerchip<br>
> <<a href="mailto:peter.millerchip@gmail.com">peter.millerchip@gmail.com</a>> wrote:<br>
>><br>
>> Yes, I agree too - trunk should ideally not contain non-working code.<br>
>> Maybe non-working drivers belong in a branch until they've been fully<br>
>> tested?<br>
>><br>
>> Maybe trunk should be locked to everyone except a "trunk manager" who<br>
>> accepts patches from people, or merges different branches in to trunk.<br>
>> That way trunk can remain stable and lean. Would that be a good idea,<br>
>> or a bad one?<br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org">Ros-dev@reactos.org</a><br>
<a href="http://www.reactos.org/mailman/listinfo/ros-dev" target="_blank">http://www.reactos.org/mailman/listinfo/ros-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Andrew Faulds (andrewros)<br><a href="http://ajf.me/">http://ajf.me/</a><br><br>