1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking Benchmarking Platform
Phoromatic Test Orchestration

Proposed Process Changes For X Server 1.8

X.Org

Published on 26 September 2009 12:10 PM EDT
Written by Michael Larabel in X.Org
21 Comments

While the X.Org developers are responsible for a lot of critical code and much of it is quite old and massive, they are often challenged by hitting a release on time and often face multiple release schedules before coming close to delivering a new X Server / X.Org release. Just take a look at X.Org 7.4 Finally Released, X.Org 7.5 Released. Wait, Nope!, or X Server 1.4.1 Is Released, No Joke as recent examples. With the X Server 1.7 / X.Org 7.5 release cycle that we are finally getting close to ending, it took multiple tries and is coming out over six months later than expected. Granted, there is Multi-Pointer X support and other new improvements, but concerns about the degrading quality of releases have been voiced for years. Fortunately, this situation may finally turn around.

Peter Hutterer, who has been working on the X.Org input code for some time and is the developer behind MPX, late into the X.Org 7.5 release cycle decided to step up to the plate and personally get this important X.Org update out the door. Peter is not stopping after X Server 1.7, but has already made a proposal regarding the release and development changes going forward for X Server 1.8 and into the future.

Peter acknowledges the current key problems with the X.Org release schedule being unpredictable, Git master is unusable at times, and there is a late testing cycle. Mr. Hutterer is proposing three fundamental changes and they include the use of feature branches, three stages to the development cycle, and predictable time-based releases. With regard to feature branches, Peter proposes that all work that is large and potentially disruptive to the X Server stability should first be done in a branch of the X Server rather than in Git master. Once the branch is developed, tested, and fairly sane it could then be pushed along into the master branch. Peter cites his Multi-Pointer X development work last year as a good example of a feature branch working out well.

The three stages of the proposed development cycle for X.Org would be feature merge, bug-fix, and release freeze. The merge window for the X Server would be open for about three months at a time followed by two months of bug-fixing and then a one month period for the X Server to be frozen and well-tested prior to a release. This would allow consistent six-month releases of the X Server / X.Org. Albeit with different time lengths, this would put the X.Org development process much closer to that of the Linux kernel. Feature branches ready for the next release would be merged into Git master during that time, followed by bug-fixing afterwards, and then at the end it's time to cut the release and then branch the X Server. The X Server would not be branched in advance of a release, but rather afterwards and prior to the next release's merge window opening.

Lastly, Peter calls for predictable time-based releases and not to delay any releases based upon half-complete features. As part of getting X.Org released on time, he also calls for monthly snapshots of Git master for easier testing and then towards the end of the cycle to provide weekly or bi-weekly snapshots until the release candidates are pumped out. Having predictable time-based releases would please quite a lot of people, especially the distribution vendors that have been challenged in the past by deciding whether they can switch to the next X.Org / X Server in their development cycle or whether delays will jeopardize the move and postpone it to their next release.

Peter's mailing list message that outlines this proposal for X Server 1.8+ can be read on xorg-devel. As of right now there are no replies to his thread, but hopefully that will change and a version of this proposal will become policy for X.Org going into the future.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux News
  1. Pinos Is For Linux Video What PulseAudio Is For Audio
  2. Crossing 200,000 Benchmark Results Posted On LinuxBenchmarking.com
  3. New Mesa Vec4 Backend For Intel, Supports Their NIR Goals
  4. "PulseVideo" Coming To Complement PulseAudio?
  5. Premium Users Now Can Experience Our New Site
  6. XFS Will Get DAX Support In The Linux 4.2 Kernel
  7. X.Org Server Lands More Mode-Setting/GLAMOR Improvements, But No Sign Of 1.18
  8. Linux Mint 17.2 Officially Released With Cinnamon/MATE Flavors
  9. Fedora For MIPS Is Now Out In Testing, Supports The Creator CI20
  10. KDE Plasma 5.3.2 Fixes Shutdown Scripts, Few Dozen Other Bugs
Latest Articles & Reviews
  1. How KDE VDG Is Trying To Make Open-Source Software Beautiful
  2. Attempting To Try Out BCache On The Linux 4.1 Kernel
  3. CompuLab's Fitlet Is A Very Tiny, Fanless, Linux PC With AMD A10 Micro
  4. AMD A10-7870K Godavari: RadeonSI Gallium3D vs. Catalyst Linux Drivers
Most Viewed News This Week
  1. Kubuntu 15.10 Could Be The End Of The Road
  2. Linus Is Looking Forward To Merging KDBUS, But Not Convinced By Performance
  3. NVIDIA Starts Supplying Open-Source Hardware Reference Headers
  4. KDBUS Won't Be Pushed Until The Linux 4.3 Kernel
  5. Linux 4.2 Kernel Gets Port To New Processor Architecture
  6. The Staging Pull For Linux 4.2: "Big, Really Big"
  7. The State & Complications Of Porting The Unity Editor To Linux
  8. SteamOS "Brewmaster" Is Valve's New Debian 8.1 Based Version