State of the release process

Sönke Ludwig sludwig at outerproduct.org
Mon Jan 12 08:59:46 UTC 2026


Over the past two years, the release process seems to have degraded 
considerably and I'm wondering where we currently stand and where we aim 
to be in the future. Some things to consider:

1. Much lower release cadence
2. No point releases anymore
3. In particular, critical macOS blockers not getting sorted by a point 
release
4. No beta releases anymore
5. No release announcement anymore
6. Regressions not receiving the priority they used to
7. New compiler releases introducing a lot more regressions that they 
used to, including in core infrastructure: 
https://github.com/dlang/dub-registry/pull/605

Personally, this feels like the times before we had the Buildkite 
project tester pipeline and every release broke something. I know 
getting the release scripts migrated and sorted has played a big role in 
this and lack of manpower in areas concerning bug fixing may also be an 
issue, but the major part seems to be an issue of project management.

So, the question is, are there plans to work towards getting back to the 
pre-2.110.0 release standards, or is this just the mode of operation to 
be expected?


More information about the Digitalmars-d mailing list