Many projects have unofficial "patch managers": http://producingoss.com/en/share-management.html#patch-manager
People who go through outstanding issues, ensuring that each has reached a stable state, or at least a willing reviewer. -C On Mon, Feb 2, 2015 at 3:45 AM, Steve Loughran <ste...@hortonworks.com> wrote: > > Given experience of apache reviews, I don't know how much time to spend on > it. I'm curious about Gerrit, but again, if JIRA integration is what is > sought, Cruicible sounds better. > > Returning to other issues in the discussion > > 1. Improving test times would make a big difference; locally as well as on > Jira. > > 2. How can we clear through today's backlog without relying on a future piece > of technology from magically fixing it? > > For clearing the backlog, I don't see any solution other than "people put in > time". I know its an obligation for committers to do this, but I also know > how little time most of us have to do things other than deal with our own > tests failing. As a result, things that aren't viewed as critical get > neglected. Shell, build, object stores, cruft cleanup, etc, I think people > that care about these areas are going to have to get together and sync up. > For some of the stuff it may be quite fast —people may not have noticed, but > a few of us have brought the build dependencies forward fairly fast recently, > with a goal of Hadoop branch-2/trunk being compatible with recent Guava > versions and java 8. > > I've been doing some S3/object store work the last couple of weekends; that's > slow as test runs take 30+ minutes against the far end, test runs jenkins > doesn't do. If anyone else wants to look at the fs/s3 and fs/swift queue > their input is welcome. > > And of course AW went through the entire backlog of shell stuff & a lot of > the not-in-branch-2 features. > > So where now? What is a strategy to deal with all those things in the queue? > > > >
