Dear centos-devel'ers, We have a problem that needs fixing. The strategy to release testable rpms to dev.centos.org, then request feedback and move the rpms to stable, when we have enough positive - isnt working. We're not getting that feedback, either positive or negative. End result is that we have packages going stale and now some of those packages need updates in themselves. Looking at the logs, I can assure you that people are using those packages, just not telling us anything about them. There is one chain of though, that such request based qa process's dont work and have been tried by other Open Source projects before and not really had much of a success rate. Now, there are a few options and alternative process's that I've been thinking about, but rather than throw that out here, I'd really like to see what everyone on this list thinks and what options / process's / workaround's we might be able to come up with here. So the issue : The CentOS Project provides packages in addition to the packages from RH's sources. We need to ensure that these packages are tested in a user environment for a while, and only released to the public via the mirror.centos.org network once there is some reasonable surety as to the functional and bugs situation with the package. ideas / comments / noise welcome.. -- Karanbir Singh : http://www.karan.org/ : 2522219 at icq