RHN, errata and QA

[Christopher McCrory <chrismcc gmail com>]

Hello...

	Todays (and yesterdays) Errata reminded me of an issue I'd like to
bring up to the RedHat guys.  Is it possible to have a QA channel, QA
list w/ package URL, or something similar?

	For an enterprise network updates usually go first to test/devel
servers for sanity checks.  Does the update break our apps?  After
some testing it is rolled out to the production machines.  For
important packages, in my case apache/php, testing can take a week or
more.  From my point of view, it would be nice to be able to QA the
Errata releases at the same time RH QA does.  Especially for security
issues that really should be pushed out quickly.

	Another benefit is knowing updates are coming down the pipe.  
Updating across a large number of production servers can take some
time, especially when you take into account checking and updating LIDS
(tripwire/aide/etc).  Seeing another Errata released just as you
finish the last one can be, ah, aggravating.  But as a bonus the whole
process is tedious. :)
	

yes? no? maybe?
Other ideas?


-- 
Christopher McCrory
 "The guy that keeps the servers running"