[ros-dev] Trunk stability

Aleksey Bragin aleksey at studiocerebral.com
Thu Oct 19 11:11:50 CEST 2006


On Oct 18, 2006, at 11:41 PM, Lucio Diaz wrote:

> Even if i am not a developer in this proyect, may I give an advice?
>
> 1) You need two trunks, one experimental, the other 1 day old  
> "booting trunk".
That's called "stable branch"

> 2)Your bot build the experimental trunk (you already have the build  
> bot).
That's how it is now

> 3) Once a day a "boot bot" would try boot the experimental trunk,  
> if it is sucessful (i supouse, sending a "all ok" message throug  
> com1) then it overwrithe the "booting trunk" with that experimental  
> revision.
It should try every revision, otherwise there is no use from it at  
all. And automerge from trunk to stable branch is not possible,  
because patches usually depend on each other.

> 4)That way there is always a very recent trunk that is stable  
> enough to boot, the testing is automatic, and you have quite  
> narrowed the revisions with the problem.
Unfortunately world is not that easy :-)

>
> That way you could be working in a somewhat stable trunk, that can  
> not be older than 1, 2 or 3 days if the experimental is failing.
>
> Best Regards,
> Lucio Diaz-Flores


WBR,
Aleksey Bragin


More information about the Ros-dev mailing list