Hi, On Mon, May 31, Bill C Riemers wrote: [...]
It looks to me like SuSE is just blindly grabbing new packages and sticking them in the 6.1 distribution. And if I assume that testing takes only
Well, maybe it looks to you this way, but it isn't the case. We shipped 2.2.7 although 2.2.8 was available. For good reason. We have many changes in our internal version which have not been integrated in the second release of 6.1 because they could change expected behaviour. But bugfixes are somewhat different. Please note that many packages get updated due to package dependencies. We have an automated build system which ensures every package gets rebuilt when necessary. So if there's a bugfix in glibc all packages would get updated even if only a small subset would have been affected by the bug.
4 hours per update, that means they should have been testing 118 days for these updates that appeared over a course of less than one month. So the only conclusion is they are NOT in anyway testing the distribution as a while remains stable as they update it.
"The _only_ conclusion"? What about: "SuSE employees plus beta testers are more than 200 people, so it takes about half a day to give every updated package about 4 hours of testing"? We will now start testing of SuSE 6.2, which will take 450 days, because there are 900 packages ;)
Bill
-o) Hubert Mantel Goodbye, dots... /\\ _\_v -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>