RFC: xserver release planning

[Michel Dänzer]

On 2024-02-06 12:19, Enrico Weigelt, metux IT consult wrote:
> On 06.02.24 10:07, Michel Dänzer wrote:
> 
>>> #4 xorg master and xwayland have massively diverged, pretty much a fork
>>
>> Not sure what you mean by that. If you're looking at the xwayland-2x.y release branches,
> 
> Yes, e.g. xwayland-23.2 is the one used by debian (unstable).
> 
>> those drop code specific to other DDXen, since that serves no purpose for standalone Xwayland releases.
> 
> Doesn't make much sense to me.

No problem, you can just ignore it.

> IIRC, one just builds with a config that only enables Xwayland and leaves off the
> others. Note that it's not just a bunch of files removed - there're even features
> removed that happen to be ununsed by xwayland.

Only Xwayland can be built & installed from a standalone Xwayland release. Anything which is only used by other DDXen would be dead weight in the Xwayland release tarballs.


> The diff is huge (even w/o the removed files) and git history has
> diverged for almost 200 commits,

This is explained above.


> w/o any clear point-of-fork.

?

xwayland-23.2 forked from master commit 94deed272cbd ("xwayland: Use sensible defaults for rootful size"). The only commits on xwayland-* branches which aren't on master are those removing stuff specific to other DDXen. There's no divergence.


> master is still at 21.1.* while xwayland is at 23.2.* - this really
> doesn't add up to me.

It's irrelevant that the versions aren't consistent, since xserver & Xwayland are now released separately.


>>> * gitlab: add xserver-23.2 milestone (realign w/ xwayland)
>>
>> It's 2024 already. There's no point in aligning with Xwayland, which is released separately anyway.
> 
> Well, I don't think it's a good idea to split that, in the long run.

That ship sailed over 3 years ago.


-- 
Earthling Michel Dänzer            |                  https://redhat.com
Libre software enthusiast          |         Mesa and Xwayland developer