[oe] Getting patches committed
Rolf Leggewie
no2spam at nospam.arcornews.de
Thu Jan 21 23:11:54 UTC 2010
Stanislav Brabec wrote:
> org.openembedded.open (or .staging or .public)
funny thing. I was discussing something like this with RP just when you
sent this mail. It's not as straightforward as it may sound, though.
First of all, I think we'd need several, possibly unlimited number of
FFA branches. Second, RP and I agreed that security implications are a
concern if we allow commit access completely uninhibited.
>> OE needs a stronger community culture. Too many devs are just contempt
>> with "my stuff works fine for me".
>
> Not as easy as it sounds. OE is a heterogeneous environment. Knowing
> that things may break on some platform need non-trivial knowledge.
If things are non-trivial, they should be reviewed. If a committer is
unsure, when in doubt, go for a review.
I'm talking of things like new bb recipes that can really do no harm
unless someone explicitly builds them. There are still a number of them
in the bug tracker that are 2, 3 or even more years old. There really
is no excuse for that IMHO, not even "I'm not interested in the recipe
in question". Recently, I closed a significant number of tickets with
recipes that had been reinvented and committed by somebody else in the
meantime. What a waste of time on both sides
More information about the Openembedded-devel
mailing list