Coming To A Desktop Near You: X.Org 7.4
The last day and a half has been filled with X.Org articles at Phoronix... Yesterday was X Server 1.4.1, today was X Server 1.4.2, and in just a few days we will now see X Server 1.5.0. X Server 1.5.0 and X.Org 7.4 were expected to be released in tandem earlier this year, but its February then May release date had slipped with no official word of when a release would be out. There were a total of four development releases planned prior to X Server 1.5.0, and we've only had two of them so far. However, Adam Jackson has made it known on the X.Org mailing list that X.Org 7.4 will soon be released.
In this message Adam mentioned he wanted to have a last look at the bug list and address anything that looks terrifying or trivial and then make a few last technical changes. Permitting there isn't a big push by many developers to clear out the blocker bugs, we're looking at just short of three dozen blocker bugs being left open before X.Org 7.4. Due to glcore changes, Mesa 7.1 will be a requirement for X.Org 7.4 / X Server 1.5.0. Before X.Org 7.4 is declared, Adam (and any volunteers) will be running through the drivers one last time and the evdev-input 2.0 driver will also be released.
Once X.Org 7.4 is out the door, planning begins for X.Org 7.5 / X Server 1.6.0 (more Phoronix coverage at that time).
In this message Adam mentioned he wanted to have a last look at the bug list and address anything that looks terrifying or trivial and then make a few last technical changes. Permitting there isn't a big push by many developers to clear out the blocker bugs, we're looking at just short of three dozen blocker bugs being left open before X.Org 7.4. Due to glcore changes, Mesa 7.1 will be a requirement for X.Org 7.4 / X Server 1.5.0. Before X.Org 7.4 is declared, Adam (and any volunteers) will be running through the drivers one last time and the evdev-input 2.0 driver will also be released.
Once X.Org 7.4 is out the door, planning begins for X.Org 7.5 / X Server 1.6.0 (more Phoronix coverage at that time).
4 Comments