This has already been discussed at length many times and even attempted in the past. It&#39;s called a Content Management System.<br>We know exactly what&#39;s needed, the problem is getting someone to implement it, and implement it well<br>
<br><br><br><div class="gmail_quote">On Fri, Dec 18, 2009 at 2:11 PM, victor martinez <span dir="ltr">&lt;<a href="mailto:vicmarcal@hotmail.com">vicmarcal@hotmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Hi,<br>
Latelly i am finding myself(and also other Testers) arriving to big gaps of non-built isos while performing a regression testing.<br>
Most of these big gaps are caused by &quot;broken trunk&quot; while devs keep commiting.<br>
My suggestion is:<br>
-Could we create a parallel repository where the devs can continue commiting in a safe way while the trunk is automatically frozen by our buildbot when an ISO cant be created?<br>
-Just the guilty dev will have access to send the patch to the main repository, then buildbot tries to compile with the patch, detects the ISO has been correctly compilled and it automatically opens the SVN again AFTER pulling ONE by ONE(and compilling them) all the revisions sent to this second repository.<br>

<br>
Advantages:<br>
-Devs wont find the trunk closed and can commit.<br>
-Testers wont find gaps when regtesting.<br>
<br>
Disadvantages:<br>
? (fill them here)<br>
<br>
Thanks for your minute of attention. :)<br>
<br>
_________________________________________________________________<br>
<br>
<br>
_______________________________________________<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>
</blockquote></div><br>