A big update on 2.110

[Dukc]

On Thursday, 6 March 2025 at 13:30:51 UTC, Dennis wrote:
> ### Long story short
>
> To run the script that handles the release process, [to quote 
> Atila](https://forum.dlang.org/post/fiyfbeczwihhsbiudtaw@forum.dlang.org), you need a special ~~Windows~~ Linux box commisioned by the Vatican and blessed by the Pope himself. But after a ton of troubleshooting, my old laptop became such a blessed box. It's probably the third one on the planet, and I'm storing it in a safe in a nuclear bunker. :)

Thanks for the writeup - and especially the work to do this. Wow, 
that was quite a campaign to get it working!

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.

> ### Future release schedule
>
> Note that 2.110 only contains bug fixes implemented in the last 
> 7 months, not the new features of the last 7 months. Those are 
> scheduled for 2.111, which brings up a question: Iain and I had 
> the idea of skipping 2.110.1 and going straight to 2.111.0, 
> since we're so far behind. There's also been talk of slowing 
> down the amount of releases in general. What do you all think?

Good idea. There are a varying number of patch versions for each 
major version anyway. It doesn't bother me if that number is 
sometimes 1.

> ### Final words
>
> I know the whole situation is very unprofessional.

I don't think the delay itself is that unprofessional. Iain has 
an incredible load of responsibilities so it would be a surprise 
if something like this _didn't_ happen sometimes. For a small 
organisation like the Foundation I don't expect that every role 
can have a timely back up that would be there in an ideal big 
company.

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? What's 
the new ETA? Or if there's no ETA currently, what's the ETA for 
the new ETA? But you just remedied that with your post.

> I want to thank Iain for doing the thankless job of being 
> release manager, and helping us out recently when he really 
> shouldn't have had to.

+1