openmw.org

https://cdn.discordapp.com/attachments/502999428798480387/593778707827654717/unknown.png We obviously can't use Matrix if I can't have capital letters. :x It's okay, they're working on removing usernames entirely, then that won't be an issue anymore :D https://github.com/matrix-org/matrix-doc/issue...

Well … That seems to have been just Matrix the website, not Matrix the thing. Yeah, their website and surrounding infrastructure (build servers, distribution nodes, and partly the matrix.org HS) got hacked due to a publicly accessible Jenkins server and some insecure SSH settings. Amusingly enough,...

Are the rooms in that group still using the bot-based bridge?

There are excellent native IRC (hosted on matrix.org) and Discord (hosted on t2bot.io) bridges available for Matrix already.
Along with Gitter, Telegram, Facebook, and a whole heap more.

And I'm sitting here and hoping that OpenMW will migrate more towards native Matrix or something similar. I don't have anything against Discord the system, though Discord the client has been nothing but trouble for me. Notifications in particular. I can't count the number of times where it's skipped...

That is really odd, the builds have been running fine here for quite a while now. I started up a manual build though outside the usual window, and that seems to have worked, so I guess I have some debugging to do over the weekend.

akortunov wrote: ↑10 Apr 2019, 17:54 It seems build process is broken - a last nightly is dated by April 5.

Apparently I somehow managed to lose the ACS patch on my kernel just before leaving for FOSS-North, so my build VM wasn't able to boot.
Fixed that problem, and have almost finished building a new set of nightlies now.

I mean, I don't think people would overly mind if the release packages were tested as well.

Windows release builds;

32-bit
64-bit

I remembered to remove the shadows DLL from the build this time too, since it slunk in when I built nightlies.

Yeah, sorry. I've had to do a small change to the repo during the RC period, which means it hasn't been able to cleanly switch to the nightly build branch during that time. I should probably set up a separate OpenMW build environment for the RCs, but I honestly haven't had time to do that right now....

The moment the release is tagged, release packages can be built - but at the same time distro maintainers will also start bumping OpenMW. So that starts a clock to get the release out before people become confused why they're on 0.45.0 while the official site reports 0.44.0 as the latest release.