Re: RFC: xserver release planning
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
Re: RFC: xserver release planning
On 06.02.24 10:07, Michel Dänzer wrote: Hi, #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. 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. The diff is huge (even w/o the removed files) and git history has diverged for almost 200 commits, w/o any clear point-of-fork. master is still at 21.1.* while xwayland is at 23.2.* - this really doesn't add up to me. * 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. I would make sense, if the Xserver would be split into lots of different libraries with independent lifecycle, but we're far, far away from that. --mtx -- --- Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schlüssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering i...@metux.net -- +49-151-27565287
Re: RFC: xserver release planning
On 2024-02-05 21:10, Enrico Weigelt, metux IT consult 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, those drop code specific to other DDXen, since that serves no purpose for standalone Xwayland releases. There's no divergence though, Xwayland is being developed on the master branch and its release branches start from current master at the time. > * 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. > * work trough differences between master and xwayland branch and try > to align them to each other (at some point in the future they should > be pretty much equal Per above, nothing to do here. -- Earthling Michel Dänzer| https://redhat.com Libre software enthusiast | Mesa and Xwayland developer
RFC: xserver release planning
Hello folks, since Xorg server didn't have a (major) release for quite some time, I'd like to discuss how to proceed here. The major problems I'm seeing right now: #1 lots of open issues and PRs, but no release planning #2 a bunch of fixes (mostly bsd) in master, which look like they could go to 21.x maintenance releases #3 lack of server-module API specification #4 xorg master and xwayland have massively diverged, pretty much a fork I'd like to propose the following steps: * gitlab: add xserver-23.2 milestone (realign w/ xwayland) * go through open PRs, decide which branches they apply (still some bugfixes for 21.x ?) and tag them accordingly * work trough differences between master and xwayland branch and try to align them to each other (at some point in the future they should be pretty much equal * document the workflow * start documenting server-module-api * potentially deprecate some unused functions --mtx -- --- Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren GPG/PGP-Schlüssel zu. --- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering i...@metux.net -- +49-151-27565287
