[oe] Switching SCM to git and commit/review policy

[Tom Rini]

On Tue, Jun 24, 2008 at 08:33:06PM +0200, Koen Kooi wrote:
> Graeme Gregory wrote:
> >>We've not made any decisions on what the commit/review policy should be,
> >>this is open for discussion. We're thinking it may take the form of some
> >>kind of kernel style Signed-off-by: tags and a switch to a partially
> >>pull based model rather than just push based as we use monotone so more
> >>than one developer handles any given change.
> >>
> >I have been thinking on this and here is my suggestion.
> >
> >One thing that has been noted has been the high level of work required
> >to review every change to every package.
> >
> >Every time more than two OE people get together we keep talking about
> >splitting OE into two. Maybe it is time to consider actually doing it.
> >My suggestion would be along the rough lines of the following.
> >
> >1) OE-core - everything needed to get upto a successful glibc build
> >completed so gcc, gcc-cross, binutils and support packages. Also most
> >stuff in classes/. Breakages in these two areas are what hurts the most
> >and the area we have the least manpower in.
> 
> I'd expand that area to the stuff task-boot covers (init, udev, busybox, 
> etc), and maybe even packages/linux.

Maybe this is too big a wish, but how about we go so far as to say a set
of distributions, machines and image targets That Will Build is the
core and everything else is the universe.  It might take a little work
to get there of course.

-- 
Tom Rini