| |||||||||||||
Testing the bleeding edgeTesting the bleeding edgePosted Mar 2, 2006 7:34 UTC (Thu) by danieldk (guest, #27876)Parent article: Testing the bleeding edge
"It's only through serious use that one discovers, say, that the web server does not handle load as well as before, that the compiler produces bogus code in certain situations, that emacs feels pretty today, or that the Wesnoth sound effects have stopped working."
True, but serious testing also occurs on stable distributions. E.g. a lot of people run a stable distribution, and install the latest version of, say, OpenOffice.org.
Distributions are now much more feature-driven than they used to be. Beta releases of some distributions include beta releases of gcc, GNOME, et al. This speeds up software development a bit, but is not really good for the quality of the final product.
(Log in to post comments)
Testing the bleeding edge Posted Mar 2, 2006 13:13 UTC (Thu) by PaulDickson (subscriber, #478) [Link] True, but serious testing also occurs on stable distributions. E.g. a lot of people run a stable distribution, and install the latest version of, say, OpenOffice.org.But this will not provide any testing of packages that OpenOffice.org depends on or is dependent on OppenOffice.org. Somewhere this has got to be tested or there will be no stable distribution. Testing with the stable distribution is far too limited.
Testing the bleeding edge Posted Mar 2, 2006 17:31 UTC (Thu) by danieldk (guest, #27876) [Link] Of course, I fully agree. But there is a difference between putting out a testing distribution with stable software versions, and putting out a testing distribution with beta software.
|
|||||||||||||