On Aug 5, 2009, at 7:50 AM, Karanbir Singh <mail-lists at karan.org> wrote: > On 08/04/2009 12:30 AM, Ross Walker wrote: >> Ok, then, is there a procedure outline for submission and maintenance >> that I should follow? > > Nothing that allows you to get anything done 'easily', but perhaps > this > is a good chance for us to fix that problem. Ok, I'll play. How about, package maintainers will test that their package works correctly on all architectures and platforms their package supports, they will then submit the SRPM to enter in the next "scheduled" build cycle, if it builds clean they should hear nothing, but if it fails they should get the error report emailed back to them, they will then need to fix and re-submit for the next build cycle. The CentOS team will discard any new SRPMs that fail to build. This puts the pressure on the maintainer to make sure it is thoroughly tested for all supported architectures and releases that they support. -Ross