Merge Review

[Jason L Tibbitts III]

>>>>> "CW" == Chris Weyl <cweyl at alumni.drew.edu> writes:

CW> As time wore on, for a variety of reasons the decision was made
CW> (by FESCo?) to treat the review tix as "advisory" and not blocking
CW> a package's inclusion in the Brave Merged World.

It's should be pretty obvious to anyone that even assuming quick
responses from the maintainers, we just didn't have the review pool
necessary to get those merge review tickets done in time for F7.  A
bunch of us locked ourselves in a room at fudcon and still didn't make
all that much progress.  It was just too much work.

CW> Now that we've achieved BMWness and F-7 is out the door, I think
CW> there should be a renewed emphasis on merge reviews, with a
CW> timeframe and actual consequences for non-review.

Well, first I'd like to see some information from Red Hat folks about
what we can actually require.  What kind of enforcement can we get?
Can someone actually force maintainers to deal with their merge review
comments?

RHEL5 and F7 are out, so it seems that we're in a good position to
find just a little developer time and hopefully we can make a dent in
them.

But currently I'm trying to make more progress on the other review
tickets, because I feel that the new contributor experience is more
important right now.  Only after that is under control do I want to
spend more time doing merge reviews (besides those which I've promised
to do).

 - J<