Re: [ros-dev] Another SVN repository...

[Ged Murphy]

This has already been discussed at length many times and even attempted in
the past. It's called a Content Management System.
We know exactly what's needed, the problem is getting someone to implement
it, and implement it well



On Fri, Dec 18, 2009 at 2:11 PM, victor martinez <vicmarcal(a)hotmail.com>wrote;wrote:

>  
>
>  Hi,
>  Latelly i am finding myself(and also other Testers) arriving to big gaps of
>  non-built isos while performing a regression testing.
>  Most of these big gaps are caused by "broken trunk" while devs keep
>  commiting.
>  My suggestion is:
>  -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?
>  -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.
>
>  Advantages:
>  -Devs wont find the trunk closed and can commit.
>  -Testers wont find gaps when regtesting.
>
>  Disadvantages:
>  ? (fill them here)
>
>  Thanks for your minute of attention. :)
>
>  _________________________________________________________________
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>