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

[Tom Rini]

On Tue, Jun 24, 2008 at 10:51:17PM +0200, Florian Boor wrote:

> Hi,
> 
> Tom Rini wrote:
> 
> > 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.
> 
> I think we are moving into mixing up a development branch with a semi-stable
> testing branch again. You can't replace motivated developers with strict policies.

I don't know..  I guess it's a question, and it can (should even) be
addressed after the git switch.  Just how wild and unstable are we still
willing to have the "main" tree be.  It sounds like there's already
agreement that big changes (thinking of packaged-staging, which is quite
nice!) will be done in a branch first.  And there's already an
autobuilder.  It seems like the next logical step would be to say what
has to be working, in order for a big changing-lots-of-things merge to
go in.  That to me would be the "core" of distros/machines/images that
need to still function.

Also, I'm not saying that for every commit to the core you need to do a
from scratch build of all combinations, but you should reasonably
confident that things work.

-- 
Tom Rini