March 06

On Thursday, 6 March 2025 at 20:33:20 UTC, Dukc wrote:

>

Since your box runs NixOS as the host OS, I guess you can pass its configuration.nix to the Foundation, so when it comes a time to set up a fourth box someday it should be at least a bit easier.

Indeed, that was one of the reasons I chose NixOS even though I'm more experienced with Debian and Arch at the moment: I wanted to have a comprehensive and reproducible list of dependencies.

>

The only gripe I have is about keeping the users up to date when the release doesn't happen when it was planned to. Why?

I understand. I think this also comes down to the delay in communication you get from distributed remote work. Concretely: I was on vacation on February 1st, and missed the DLF monthly meeting on February 7th. On the 14th I had my bi-weekly check-in with Mike and Razvan, and I heard that the 2.110 release situation came up in the monthly meeting, and that Robert and Iain were working on the changelog generator. I guess at that point I could have made an announcement, but I had hardly any details. I couldn't tell if it was going to be sorted out next week or actually another major delay. It wasn't the top idea in my mind either: I had my own work to get back to.

With online correspondence it's so easy for days to pass between messages, or even weeks when one party forgets to follow up. It's like what Walter always stresses: issues that are going on for months can be hashed out at DConf in minutes, where we're all in person.

March 07
On Thursday, 6 March 2025 at 13:30:51 UTC, Dennis wrote:
> Hello everyone,
>
> ...

Nice story and a bit scary one. There must have be good relief in the end.

We should be glad to have people that give up their own time to maintain projects like this.

Thanks for your work,

Matheus.
March 07

On Thursday, 6 March 2025 at 13:30:51 UTC, Dennis wrote:

>

Hello everyone,

[...]

~Dennis Korpel

Unfortunately, what is released as 2.110 differs from what's in the 2.110.rc.1 .

Not by much, but by enough so that the release doesn't build SDC even though rc.1 does.

I'm a bit frustrated because all my CI pipelines are now broken, even though I test the beta channel and rc to make sure I don't find myself in that spot. What's the point of making a rc if this is not going to be what is shipped?

Anyways, this is the failure I'm getting: https://github.com/snazzy-d/sdc/actions/runs/13713868682/job/38372203222

March 07

On Friday, 7 March 2025 at 12:24:54 UTC, deadalnix wrote:

>

On Thursday, 6 March 2025 at 13:30:51 UTC, Dennis wrote:

>

Hello everyone,

[...]

~Dennis Korpel

Unfortunately, what is released as 2.110 differs from what's in the 2.110.rc.1 .

Not by much, but by enough so that the release doesn't build SDC even though rc.1 does.

I'm a bit frustrated because all my CI pipelines are now broken, even though I test the beta channel and rc to make sure I don't find myself in that spot. What's the point of making a rc if this is not going to be what is shipped?

Anyways, this is the failure I'm getting: https://github.com/snazzy-d/sdc/actions/runs/13713868682/job/38372203222

I was able to reduce this to https://github.com/dlang/dmd/issues/20965 .

The reduced error happens in 2.109 as well, and I assume it now triggers in the overall project in 2.110 and not 2.109 because the template instactiation order changed somehow.

March 07
I big thank you to Dennis and Iain for the tremendous amount of work solving this problem!

I hope Iain gets better soon!
1 2
Next ›   Last »