On Wed, 18 Dec 2002, Dave Jones wrote:
>
> > I just don't know what that "something" should be. Any ideas? I thought
> > about the code freeze require buy-in from three of four people (me, Alan,
> > Dave and Andrew come to mind) for a patch to go in, but that's probably
> > too draconian for now. Or is it (maybe start with "needs approval by two"
> > and switch it to three when going into code freeze)?
>
> You'd likely need an odd number of folks in this cabal^Winner circle
> though, or would you just do it and be damned if you got an equal
> number of 'aye's and 'nay's ? 8-)
Quite frankly, I wouldn't expect a lot of dissent.
I suspect a group approach has very little inherent disagreement, and to
me the main result of having an "approval process" is to really just slow
things down and make people think about the submitting. The actual
approval itself is secondary (it _looks_ like a primary objective, but in
real life it's just the _existence_ of rules that make more of a
difference).
> The approval process does seem to be quite a lot of work though.
> I think it was rth last year at OLS who told me that at that time
> he'd been doing more approving of other peoples stuff than coding himself.
I heartily disagree with the approval process for development, just
because it gets so much in the way and just annoys people. But for
stabilization, that's exactly what you want. So I think gcc is using the
approval process much too much, but apparently it works for them.
And I think it could work for the kernel too, especially the stable
releases and for the process of getting there. I just don't really know
how to set it up well.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:20 EST