Re: [ros-dev] Regression fixing

[Olaf Siejka]

Then again, how would you propose to deal with regressions that will for
sure slip in at periods of time, when trunk is not buildable or doesnt boot?

For example, inbetween ac97 driver install breakage range - rev: 46977-47057
i counted at least 4 regressions that were introduced in revisions
inbetween.

2010/4/30 James Tabor <jimtabor.rosdev(a)gmail.com>

>   Hum?
>
>  On Thu, Apr 29, 2010 at 5:45 PM, Olaf Siejka <caemyr(a)gmail.com> wrote:
> >   The most important reason for moving development
> > into branches was to
> >  minimize the effect of prolonged trunk breakage, that has to happen with
> >  rewrites. This is a vital issue, as inability of testing trunk on the 
>  daily
> >   basis is very often a seed for regression
> > accumulation.
> >  
>  If we had one hundred or more full time developers, this might work.
>  We don't so it's not working and it is creating a mess and losing the
>  little time we have in branches. The argument that was pushed and
>  posted by the developers that left the project recently objected to
>  dividing resources in regards of the other project branch (which
>  should have remained as a research project and not the official
>  replacement of a ReactOS subsystem) thus proving them correct.
>
>  Look at this as a signal warning before the shit hits the reef.......
>  The ship has turn into the reef!
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>