Brainstorming tasks for next sprint

John Eckersberg jeckersb at redhat.com
Tue Feb 14 15:59:05 UTC 2012


On Tue, 14 Feb 2012 10:46:24 -0500, Jason Guiditta <jguiditt at redhat.com> wrote:
> Better patch management than just sending to list.  This is a _very_
> long-standing issue that we need to attempt (again) to resolve.  I am
> not against trying pull requests in github (probably on some trial
> basis, with a small group vetting it and assembling feedback, so as to
> not throw everybody off on something we may or may not keep).  There
> are also a number of other projects around for this kind of thing that
> we could pilot - patchwork and gerrit in the public space, and our own
> (not the best name) trapaas, that resulted from some work mzatko did
> for me when he was an intern (think the code is on github, not sure in
> what state).  I am sure there are plenty of other options we coudl
> consider, these are just a couple I remember from last tiem I looked
> at this problem.  But the fact remains - the list is a poor patch
> management tool, and is insufficient for our needs.

Yes, this.  I'm curious, given the "attempt (again)" bit, what has been
done in the past to try and correct this (and ultimately failed)?



More information about the aeolus-devel mailing list