Call for testing of xserver 1.20 release candidates

[Adam Jackson]

Short version:

$ sudo dnf copr enable ajax/upstream
$ sudo dnf upgrade

Long version:

I've set up a copr containing a rebuild of the X server and drivers for
the upstream 1.20 release candidates. Unfortunately the upstream and
Fedora schedules didn't line up as well as I'd have liked, so I'm not
going to try to land this for F28 GA. But I would _very_ much like to 
push this as an update, and would appreciate any and all testing and
feedback.

- ajax

[Kalev Lember]

On 03/05/2018 05:48 PM, Adam Jackson wrote:
>  Short version:
>  
>  $ sudo dnf copr enable ajax/upstream
>  $ sudo dnf upgrade
>  
>  Long version:
>  
>  I've set up a copr containing a rebuild of the X server and drivers for
>  the upstream 1.20 release candidates. Unfortunately the upstream and
>  Fedora schedules didn't line up as well as I'd have liked, so I'm not
>  going to try to land this for F28 GA. But I would _very_ much like to 
>  push this as an update, and would appreciate any and all testing and
>  feedback. 
I would say the opposite: land this today so that it can get in F28 Beta
(tomorrow starts package freeze for the beta release), and don't do a
post release update that changes the drivers ABI.

This way, you get all the Fedora QA testing that's done as part of the
release with the new xserver code, and avoid a disruptive post release
update that invalidates all the QA testing + creates a problematic ABI
change.

-- 
Kalev

[William Moreno]

>  I would say the opposite: land this today so that it can get in F28 Beta
>  (tomorrow starts package freeze for the beta release), and don't do a
>  post release update that changes the drivers ABI.
>
>  
This should have happened via the System Wide Changes proces, isn´t? At
less a Freeze exception should be requested, even with WorkStation using
wayland by default the Xserver is critical for the others spins, in the
works case can land in F29.

[Adam Jackson]

On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote:
>  On 03/05/2018 05:48 PM, Adam Jackson wrote:
>  > Short version:
>  > 
>  > $ sudo dnf copr enable ajax/upstream
>  > $ sudo dnf upgrade
>  > 
>  > Long version:
>  > 
>  > I've set up a copr containing a rebuild of the X server and drivers for
>  > the upstream 1.20 release candidates. Unfortunately the upstream and
>  > Fedora schedules didn't line up as well as I'd have liked, so I'm not
>  > going to try to land this for F28 GA. But I would _very_ much like to 
>  > push this as an update, and would appreciate any and all testing and
>  > feedback.
>  
>  I would say the opposite: land this today so that it can get in F28 Beta
>  (tomorrow starts package freeze for the beta release), and don't do a
>  post release update that changes the drivers ABI. 
Much as I would like to, the change process does exist, and says it's
far too late for that for F28 gold.

- ajax

[Leigh Scott]

>  On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote:
>  
>  Much as I would like to, the change process does exist, and says it's
>  far too late for that for F28 gold.
>  
>  - ajax 
Can't  new Xorg wait till F29?,  isn't this change to big and prone
to breakage to be pushed after F28 release?

[Adam Jackson]

On Tue, 2018-03-06 at 12:57 +0000, Leigh Scott wrote:
>  > On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote:
>  > 
>  > Much as I would like to, the change process does exist, and says it's
>  > far too late for that for F28 gold.
>  
>  Can't  new Xorg wait till F29?,  isn't this change to big and prone
>  to breakage to be pushed after F28 release? 
That I'm suggesting doing it is evidence that I think it should be safe
to do. We've rebased llvm in live releases and that's far more
disruptive.

- ajax