$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> X.org Rethinks Release Strategy » Linux Magazine
 

X.org Rethinks Release Strategy

Oct 01, 2009

The X.org project has some discussion ahead of it, instigated by developer Peter Hutterer's call for an ordered release strategy. The current rather unpredictable release schedule makes the work and test process harder, according to Hutterer.

In Hutterer's entry on the X.org mailing list he identifies some problems in the current development process leading to the current unpredictable release schedule. The most recent example was version 1.7 with its currently changing milestones and a code freeze and final release "out of nowhere."

Hutterer's suggestion is to introduce a three-stage model similar to that used in kernel development: feature merge, bugfix, and release freeze. Every stage should have its distinct milestones, thereby achieving predictable releases. The predictability should enable project and external developers to test their code more easily. Hutterer's suggestion is corroborated by others and discussion is likely to follow.

comments powered by Disqus

Issue 152/2013

Tag Cloud

Bruce Byfield Gnome KDE Kernel Linux Linux Pro Magazine Open Source Projects Red Hat Ubuntu events foss free software google

News