Linked by Thom Holwerda on Tue 25th May 2010 15:44 UTC, submitted by Philipp Esselbach
Permalink for comment 426525
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-07-06
Seriously if you really need the latest, you could download the SRPMS and set up some script that makes nightly builds from subversion or something, but then you should probably create some kind of test suite, that tests you system before it upgrades.
Just because the developer have shipped a later release doesn't always mean that it is well tested by somebody else than the developers. You could argue that developers should test their own code, and they should, but the problem is that you tend to get blind to your own errors, so to be well tested a program should really be tested by somebody with a users perspective rather than a developers perspective.
This is one of the reasons it takes some time to assmble a linux distro. Even though Fedora is supposed to be bleeding edge, there need to be some form of QA for it to be usable, even for less mission critical things