Linux.com

Re:time based releases

Posted by: Administrator on March 29, 2007 06:29 AM
Today, If I take the vanilla Fedora Core6 DVD, and install KDE, GNOME, and essentially every other application, my yum update advisory program (pup) tells me that to bring my system up to date, I have to download more than 350 modules.

I can tell you that if I accept the ones for X and Kernel, my system will not boot. But I can accept the others.



My other experience has been with RPM / YUM failing because of a faulty update to some component. I have learned that these two critical softwares use shared libraries, and one of the non-mainstream applications updated one or more of these, and that update caused the YUM failure.

Automated testing did not have find this problem, as neither YUM or RPM was modified, I will not conjecture why.



So, automated testing or no automated testing, as the number of applications / modules increases, the testing time / schedule should also increase, particularly if we want to maintain quality.

Any loss in quality/reliablity is wonderful ammunition to the two major competitors.

I am very much in favor of moving to a 9-12 month release schedule. To accomodate the must have individuals, the test versions could be "forked" so that they may enjoy their daily updates.

#

Return to Michlmayr advocates time-based release management for FOSS projects