March 05

On Wednesday, 5 March 2025 at 01:45:32 UTC, Paul Backus wrote:

>

If a project repeatedly fails to achieve the goals it sets for itself, that does not generally bode well for the project's future.

This is a consequence of having a complex release process that's dependent on one person, and not a reflection on anything beyond that. In hindsight, it's surprising that it hasn't happened before now.

The upside is that it's highlighted the necessity to simplify and de-bottleneck the release process so that when the primary is unavailable, someone else can handle it.

March 05

On Wednesday, 5 March 2025 at 03:38:27 UTC, Mike Parker wrote:

>

On Wednesday, 5 March 2025 at 01:45:32 UTC, Paul Backus wrote:

This is a consequence of having a complex release process that's dependent on one person, and not a reflection on anything beyond that. In hindsight, it's surprising that it hasn't happened before now.

And for the record, a release candidate has been available for download for a few weeks. The holdup, as Johnathan mentioned, was an issue with the changelog resulting from the Bugzilla to GitHub migration. Robert recently updated the PR to fix it, and Iain left some review comments yesterday:

https://github.com/dlang/tools/pull/466

March 05

On Wednesday, 5 March 2025 at 03:38:27 UTC, Mike Parker wrote:

>

On Wednesday, 5 March 2025 at 01:45:32 UTC, Paul Backus wrote:

>

If a project repeatedly fails to achieve the goals it sets for itself, that does not generally bode well for the project's future.

This is a consequence of having a complex release process that's dependent on one person, and not a reflection on anything beyond that. In hindsight, it's surprising that it hasn't happened before now.

The upside is that it's highlighted the necessity to simplify and de-bottleneck the release process so that when the primary is unavailable, someone else can handle it.

I bet adr could make a binary whenever you want. V2.110++ would be a fantastic release

March 05
On 05/03/2025 6:18 PM, monkyyy wrote:
> On Wednesday, 5 March 2025 at 03:38:27 UTC, Mike Parker wrote:
>> On Wednesday, 5 March 2025 at 01:45:32 UTC, Paul Backus wrote:
>>
>>>
>>> If a project repeatedly fails to achieve the goals it sets for itself, that does not generally bode well for the project's future.
>>
>> This is a consequence of having a complex release process that's dependent on one person, and not a reflection on anything beyond that. In hindsight, it's surprising that it hasn't happened before now.
>>
>> The upside is that it's highlighted the necessity to simplify and de- bottleneck the release process so that when the primary is unavailable, someone else can handle it.
> 
> I bet adr could make a binary whenever you want. V2.110++ would be a fantastic release

The nightlies are almost identical to the release binaries, they are in no way shape or form what is limiting it.

There is a lot more to the release _process_ than just making a binary.

I.e. change log handling, which is held up by the migration to GitHub issues.

March 05

On Wednesday, 5 March 2025 at 01:45:32 UTC, Paul Backus wrote:

>

Nobody would be worried if we were switching to a yearly release cadence on purpose. What worries people is that we've set targets for the release of 2.110.0 and missed them, repeatedly, without intending to.

If a project repeatedly fails to achieve the goals it sets for itself, that does not generally bode well for the project's future.

It may be a bit anecdotal but we don't seem to have suffered for it. While NG traffic may be down, the Discord has been picking up quite a few new faces recently and text-traffic in there is as high as it's ever been. YMMV and all. 🤷‍♂️

IMO, the fact that it hasn't been a major problem would suggest that our current cadence might be a bit too intense. And a slower cadence would reduce updating/maintenance work for those of us who run build-farms.

March 06

On Tuesday, 4 March 2025 at 23:08:37 UTC, Adam Wilson wrote:

> >

The project isn't viable if it can't release.

Nobody says this about other languages despite them being on much longer release timelines. C++ is three years. Rust editions are three years. C# is yearly. Java is twice yearly.

That is language version schedules, not compiler version schedules. There are updates to MSVC around every few months.

>

In the grand scheme of things a yearly release cadence is actually pretty quick.

For languages, yes. For compilers, no.

March 07

On Thursday, 6 March 2025 at 00:08:00 UTC, Quirin Schroll wrote:

>

On Tuesday, 4 March 2025 at 23:08:37 UTC, Adam Wilson wrote:

> >

The project isn't viable if it can't release.

Nobody says this about other languages despite them being on much longer release timelines. C++ is three years. Rust editions are three years. C# is yearly. Java is twice yearly.

That is language version schedules, not compiler version schedules. There are updates to MSVC around every few months.

>

In the grand scheme of things a yearly release cadence is actually pretty quick.

For languages, yes. For compilers, no.

But that's exactly what I am talking about. MSVC gets regression/critical fixes monthly, standard bug fixes and features every 3 months, and ISO Standard upgrades every three years.

What I suggested isn't materially different. With the caveat that we're not an ISO standard so we get to choose our language feature release cadence.

We can do monthly point release for ice/regressions/critical fixes and then say 6 months for features and standard bug fixes.

March 07
On Wednesday, 5 March 2025 at 09:15:20 UTC, Adam Wilson wrote:
> ...
> It may be a bit anecdotal but we don't seem to have suffered for it. While NG traffic may be down, the Discord has been picking up quite a few new faces recently and text-traffic in there is as high as it's ever been. YMMV and all. 🤷‍♂️
> ...

I don't understand why not using the NG as a main medium. Relying on other social tool my be mistake, information may be lost and people need to sign up to most of those "free services".

This NG is so easy to talk and pretty much is all easily archived by default.

I think this fragmentation of communication is not good.

You should ask them to come here.

Matheus.
March 11
On Friday, 7 March 2025 at 11:16:45 UTC, matheus wrote:
> I don't understand why not using the NG as a main medium. Relying on other social tool my be mistake, information may be lost and people need to sign up to most of those "free services".
>
> This NG is so easy to talk and pretty much is all easily archived by default.
>
> I think this fragmentation of communication is not good.
>
> You should ask them to come here.
>
> Matheus.

Because Discord is where the bulk of the discussion happens? That's just the way things are, and we can't demand that people use the medium that we want them to. We have to go where they are.
March 11
On Friday, 7 March 2025 at 11:16:45 UTC, matheus wrote:
> This NG is so easy to talk and pretty much is all easily archived by default.

and doesn't support many things which we have in Discord.
And the Discord now is de facto standard. Many tech projects have their discord servers to handle community..

> I think this fragmentation of communication is not good.

Many people are reading both..

> You should ask them to come here.

Most probably it is not gonna happen..
We had a poll there

> To interact with D community (asking/answering questions) I:
> prefer to use only Discord - 13 (59%)
> prefer to use only Forum - 1 (5%)
> prefer to use both Discord and Forum - 8 (36%)