www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Why =?UTF-8?B?aXNu4oCZdA==?= 2.110 published?

reply Quirin Schroll <qs.il.paperinik gmail.com> writes:
Wasn’t 2.110 due for August 1? Is there a reason it isn’t it 
published yet?
Aug 19
next sibling parent reply Dakota <dakota gmail.com> writes:
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 am quite surprised that such a simple and important question 
has gone without any response for such a long time


I can't help but wonder what the future of the community will 
look like.
Aug 29
parent reply Sergey <kornburn yandex.ru> writes:
On Friday, 30 August 2024 at 06:36:23 UTC, Dakota 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 am quite surprised that such a simple and important question 
 has gone without any response for such a long time


 I can't help but wonder what the future of the community will 
 look like.


I already told that before..
all problems are because unrealistic expectations: people still 
considering D as a serious production language - they just need 
to stop doing it...
It is great hobby language for hobby projects.

I'm almost sure many people after reading this will have
- denial
- anger
- bargaining
- depression

When you accept this - peace and happiness will be with you :)
You no longer care about not only 2.110 but any other versions, 
bugzilla migrations and all things that are not happening. All 
bugs that haven't been fixed for years (and won't be fixed in 
another decade).. and just enjoy using the language in any way 
you like.

So stop feeling frustrated and start enjoying life!
Aug 29
parent reply Mike Parker <aldacron gmail.com> writes:
On Friday, 30 August 2024 at 06:46:54 UTC, Sergey wrote:

 On Friday, 30 August 2024 at 06:36:23 UTC, Dakota 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 am quite surprised that such a simple and important question 
 has gone without any response for such a long time


 I can't help but wonder what the future of the community will 
 look like.


 I already told that before..
 all problems are because unrealistic expectations: people still 
 considering D as a serious production language - they just need 
 to stop doing it...
 It is great hobby language for hobby projects.


Relax people. Iain Buclaw handles the releases. Anytime there's a 
delay, there's a reason for it.
Aug 30
next sibling parent ryuukk_ <ryuukk.dev gmail.com> writes:
On Friday, 30 August 2024 at 07:04:06 UTC, Mike Parker wrote:

 On Friday, 30 August 2024 at 06:46:54 UTC, Sergey wrote:

 On Friday, 30 August 2024 at 06:36:23 UTC, Dakota 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 am quite surprised that such a simple and important 
 question has gone without any response for such a long time


 I can't help but wonder what the future of the community will 
 look like.


 I already told that before..
 all problems are because unrealistic expectations: people 
 still considering D as a serious production language - they 
 just need to stop doing it...
 It is great hobby language for hobby projects.


 Relax people. Iain Buclaw handles the releases. Anytime there's 
 a delay, there's a reason for it.


Communication is key to avoid confusion and concerns, there is 
literally 0 communication, therefore there will be confusion and 
concerns
Aug 30
prev sibling parent reply Adam Wilson <flyboynw gmail.com> writes:
On Friday, 30 August 2024 at 07:04:06 UTC, Mike Parker wrote:

 Relax people. Iain Buclaw handles the releases. Anytime there's 
 a delay, there's a reason for it.


I don't think people have a problem with the concept of their 
being a reason for it. I think the problem is that there has been 
no communication, at least that I've seen on what that reason is.

It could be as simple as "Iain had to step away for a while, but 
he'll be back in X time."
Or maybe it's being held back for a gnarly problem in the build 
pipeline that needs time to get resolved.
Or maybe there is a super-secret feature being developed that 
we're waiting on.

IDK. 🤷‍♂️

The point being, we don't know why, and I think that would cool 
all of this down if we did. But the radio silence is 
disconcerting. And there is quite the pile of fixes and changes 
building up in the pending changelog.
Oct 23
parent reply M.M. <matus email.cz> writes:
On Thursday, 24 October 2024 at 06:24:56 UTC, Adam Wilson wrote:

 On Friday, 30 August 2024 at 07:04:06 UTC, Mike Parker wrote:

 Relax people. Iain Buclaw handles the releases. Anytime 
 there's a delay, there's a reason for it.


 I don't think people have a problem with the concept of their 
 being a reason for it. I think the problem is that there has 
 been no communication, at least that I've seen on what that 
 reason is.

 It could be as simple as "Iain had to step away for a while, 
 but he'll be back in X time."
 Or maybe it's being held back for a gnarly problem in the build 
 pipeline that needs time to get resolved.
 Or maybe there is a super-secret feature being developed that 
 we're waiting on.

 IDK. 🤷‍♂️

 The point being, we don't know why, and I think that would cool 
 all of this down if we did. But the radio silence is 
 disconcerting. And there is quite the pile of fixes and changes 
 building up in the pending changelog.


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.)
Oct 25
parent reply Lance Bachmeier <no spam.net> writes:
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.
Oct 25
parent reply "Richard (Rikki) Andrew Cattermole" <richard cattermole.co.nz> writes:
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.
Oct 25
next sibling parent Sergey <kornburn yandex.ru> writes:
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 :)
Oct 25
prev sibling parent reply Lance Bachmeier <no spam.net> writes:
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.
Oct 25
parent reply Mike Parker <aldacron gmail.com> writes:
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.
Oct 25
next sibling parent jmh530 <john.michael.hall gmail.com> writes:
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.
Oct 25
prev sibling parent reply Don Allen <donaldcallen gmail.com> writes:
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.
Nov 04
parent Mike Parker <aldacron gmail.com> writes:
On Monday, 4 November 2024 at 17:14:53 UTC, Don Allen wrote:


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


I have nothing else to tell you at the moment. I don't know why 
it has't been released yet, and I can't give you a date for when 
it will be. As soon as I know anything, I'll tell announce it.
Nov 04
prev sibling next sibling parent reply ryuukk_ <ryuukk.dev gmail.com> writes:
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?


what's sad is people from D foundation all ignored this post


they literally don't care about people using D

it shows in the PRs that get merged, and it shows in releases 
being ignored
Aug 30
parent Mike Parker <aldacron gmail.com> writes:
On Friday, 30 August 2024 at 07:03:11 UTC, ryuukk_ wrote:


 they literally don't care about people using D



Nothing could be further from the truth. We wouldn't be here 
otherwise.
Aug 30
prev sibling next sibling parent Dakota <dakota gmail.com> writes:
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?


Almost 3 months delay, any comment from core team?
Oct 23
prev sibling parent reply Ivan Kazmenko <gassa mail.ru> writes:
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.
Nov 03
parent reply Mike Parker <aldacron gmail.com> writes:
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.
Nov 03
parent reply Ivan Kazmenko <gassa mail.ru> writes:
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.
Nov 04
parent Mike Parker <aldacron gmail.com> writes:
On Monday, 4 November 2024 at 17:59:43 UTC, Ivan Kazmenko wrote:


 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.


Thank you. Yes, I'll announce something as soon as I know it.
Nov 04