October 25

On Friday, 25 October 2024 at 07:57:28 UTC, M.M. wrote:

>

Iain's activity on github has lowered substantially (is close to zero) since around july:

https://github.com/ibuclaw

(That would suggest that Iain is taking a break for a while; hope all is good, and the break was planned.)

But this isn't Iain's release, it's the project's release. It's very alarming that we're in a situation where everything relies on one person and nobody else knows what's going on. We don't want to blow this out of proportion, but this is what it looks like when an open source project dies. I'm not worried about that (yet) because LDC seems to be in good shape. At the same time, I'm evaluating my options in the event that we've reached the downward spiral.

October 26
On 26/10/2024 12:18 AM, Lance Bachmeier wrote:
> On Friday, 25 October 2024 at 07:57:28 UTC, M.M. wrote:
> 
>> Iain's activity on github has lowered substantially (is close to zero) since around july:
>>
>> https://github.com/ibuclaw
>>
>> (That would suggest that Iain is taking a break for a while; hope all is good, and the break was planned.)
> 
> But this isn't Iain's release, it's the project's release. It's very alarming that we're in a situation where everything relies on one person and nobody else knows what's going on. We don't want to blow this out of proportion, but this is what it looks like when an open source project dies. I'm not worried about that (yet) because LDC seems to be in good shape. At the same time, I'm evaluating my options in the event that we've reached the downward spiral.

You are over thinking this.

It is delayed, Iain is busy.

He had back to back conferences last month.

If something were to happen to Iain, somebody else would take on the job of release manager.

Ldc's releases are automated, dmd's isn't currently. We'd get it sorted out no matter what happens.

October 25
On Friday, 25 October 2024 at 11:44:42 UTC, Richard (Rikki) Andrew Cattermole wrote:
> It is delayed, Iain is busy.

At least the compiler is stable and no breaking changes :)
October 25

On Friday, 25 October 2024 at 11:44:42 UTC, Richard (Rikki) Andrew Cattermole wrote:

>

It is delayed, Iain is busy.

That's not the problem. A delay of three months (or however long it turns out to be) with no communication is not something you see when an open source project is healthy. It's a sign that all the contributors are focused on doing their own thing. Which of course they have a right to do, but then new users/adoption dries up. This combined with the death of GtkD and Visual D, and what appears to be a lack of new users, particularly business users, does not make a compelling case when comparing with other languages.

October 25

On Friday, 25 October 2024 at 12:48:02 UTC, Lance Bachmeier wrote:

>

That's not the problem. A delay of three months (or however long it turns out to be) with no communication is not something you see when an open source project is healthy. It's a sign that all the contributors are focused on doing their own thing. Which of course they have a right to do, but then new users/adoption dries up. This combined with the death of GtkD and Visual D, and what appears to be a lack of new users, particularly business users, does not make a compelling case when comparing with other languages.

One of Iain's goals is to get the release progress packaged up into basically a single button push so that anyone can do it. Once he gets to that point, we'll be able to avoid situations like this. But we aren't there yet. Until we are, it's pretty much on his shoulders.

October 25

On Friday, 25 October 2024 at 12:59:44 UTC, Mike Parker wrote:

>

On Friday, 25 October 2024 at 12:48:02 UTC, Lance Bachmeier wrote:

>

That's not the problem. A delay of three months (or however long it turns out to be) with no communication is not something you see when an open source project is healthy. It's a sign that all the contributors are focused on doing their own thing. Which of course they have a right to do, but then new users/adoption dries up. This combined with the death of GtkD and Visual D, and what appears to be a lack of new users, particularly business users, does not make a compelling case when comparing with other languages.

One of Iain's goals is to get the release progress packaged up into basically a single button push so that anyone can do it. Once he gets to that point, we'll be able to avoid situations like this. But we aren't there yet. Until we are, it's pretty much on his shoulders.

I think that's a great goal, but I think Bachmeier's point is more about the lack of communication to the community. I don't think anyone is going to beat up on Iain for being busy and needing to delay the release a few weeks, but a heads up that the release is delayed makes the organization look a little more professional.

November 03

On Monday, 19 August 2024 at 12:59:34 UTC, Quirin Schroll wrote:

>

Wasn’t 2.110 due for August 1? Is there a reason it isn’t it published yet?

I'd like to just reiterate the original question, in this form.
When could one expect a 2.110 release?

Ivan Kazmenko.

November 04

On Sunday, 3 November 2024 at 22:47:41 UTC, Ivan Kazmenko wrote:

>

On Monday, 19 August 2024 at 12:59:34 UTC, Quirin Schroll wrote:

>

Wasn’t 2.110 due for August 1? Is there a reason it isn’t it published yet?

I'd like to just reiterate the original question, in this form.
When could one expect a 2.110 release?

At the moment, we're trying to find out what's going on with Iain.

November 04

On Friday, 25 October 2024 at 12:59:44 UTC, Mike Parker wrote:

>

On Friday, 25 October 2024 at 12:48:02 UTC, Lance Bachmeier wrote:

>

That's not the problem. A delay of three months (or however long it turns out to be) with no communication is not something you see when an open source project is healthy. It's a sign that all the contributors are focused on doing their own thing. Which of course they have a right to do, but then new users/adoption dries up. This combined with the death of GtkD and Visual D, and what appears to be a lack of new users, particularly business users, does not make a compelling case when comparing with other languages.

One of Iain's goals is to get the release progress packaged up into basically a single button push so that anyone can do it. Once he gets to that point, we'll be able to avoid situations like this. But we aren't there yet. Until we are, it's pretty much on his shoulders.

It is amazing to me when I read, repeatedly

Q: Why has there been no communication about the delay of the 2.110 release?
A: Iain is busy. That's why 2.110 hasn't been released.

It is not helpful to this project when people ask a question and receive an answer to a question they didn't ask.

November 04

On Monday, 4 November 2024 at 01:36:48 UTC, Mike Parker wrote:

>

On Sunday, 3 November 2024 at 22:47:41 UTC, Ivan Kazmenko wrote:

>

On Monday, 19 August 2024 at 12:59:34 UTC, Quirin Schroll wrote:

>

Wasn’t 2.110 due for August 1? Is there a reason it isn’t it published yet?

I'd like to just reiterate the original question, in this form.
When could one expect a 2.110 release?

At the moment, we're trying to find out what's going on with Iain.

My best wishes to Iain Buclaw and other maintainers!
I hope Iain would be able to return to packaging the releases at some point.
And Mike, please keep us posted when you have an update.

Ivan Kazmenko.