Call Me Tango

> If there aren't any blockers anymore, I'd like to make the release soon. There are some organizational blockers like updating the website etc. I will create tickets and list...

@metux > are you okay with Dec 21 as release date ? Yes, I think this is realistic.

> IIRC had a few things to do left. Yes, I'd like to do some "paperwork" like finishing the "How to build XLibre", "Switching to XLibre" etc. things and create...

> XLIbre logo poll IMO this takes some time and we shouldn't hold the release for this. So my suggestion is to do it incrementally.

@metux > [@callmetango](https://github.com/callmetango) did already have some time for preparing release notes ? I'll take care of them in #1684, starting today.

@alexislefebvre > What does “As usual” mean? How packagers can learn this important information, now and in the future? Is it documented somewhere that X.Y.0 are not stable releases? We'll...

@metux I think it would be good to soft freeze the current Xserver code and stabilize it and fix bugs etc until we release `25.1.0`. We should also create a...

I created a guide for how to fix your previous pull request https://github.com/X11Libre/xserver/pull/234 in https://github.com/X11Libre/xserver/pull/234#issuecomment-3233639858.

@alexislefebvre > If you use something like https://semver.org/, you can only perform incompatible changes of the ABI in 26.x. Or explain that in the release workflow that you use, 25.1...

If we choose to accept this change than we have to make this very clear to our users. Think release notes, notable changes, etc. Otherwise it could be perceived as...