November 04 Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Don Allen | 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. | |||
November 04 Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Ivan Kazmenko | On Monday, 4 November 2024 at 17:59:43 UTC, Ivan Kazmenko wrote: >My best wishes to Iain Buclaw and other maintainers! Thank you. Yes, I'll announce something as soon as I know it. | |||
5 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Quirin Schroll | 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? We're nearing four months since missing the deadline for a release, and there's still no announcement from the leadership, and there's apparently nobody available/interested enough to finish it up. After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death. | |||
5 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Lance Bachmeier | On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier 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? We're nearing four months since missing the deadline for a release, and there's still no announcement from the leadership, and there's apparently nobody available/interested enough to finish it up. After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death. The project is nowhere near death. The compiler release is delayed, but everything else is moving along. I have nothing to announce yet because I haven't been able to confirm what's going on with Iain. I'm expecting to have that confirmation soon, at which point I'll be able to make an announcement about when he'll be able to get the next release out or someone else will. | |||
5 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Lance Bachmeier | On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier wrote: >and there's apparently nobody available/interested enough to finish it up. The release process is a multistep thing that, in its current state, is dependent on Iain. As I said earlier, he intends to simplify it so any of us could do it, but hasn’t gotten there yet. If he were abducted by aliens, one of us would step in and replace it with a new process. We aren’t at the point yet for such an extreme measure. Right now, our biggest priority here is making sure Iain is okay. Then we can figure out what to do about the releaae. | |||
5 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Lance Bachmeier | On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier 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? We're nearing four months since missing the deadline for a release, and there's still no announcement from the leadership, and there's apparently nobody available/interested enough to finish it up. After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death. I wonder what is so important about the deadly? Or are you writing software that coordinates the take-off and landing of aircraft? Is there a fatal bug report you've made in the past that hasn't been fixed yet? A As a D programmer, you have such power (ImportC) at your disposal that there is nothing you can't do despite the limitations of the language. In summary, even if there is no update for 1 year, it is not the end of life... IMO, they are now spending the time they would have spent on monthly updates to release a better version. In summary, the expectation is great and I hope that will happen before the end of the year. SDB@79 | |||
4 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Lance Bachmeier | On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier wrote: >We're nearing four months since missing the deadline for a release, and there's still no announcement from the leadership, and there's apparently nobody available/interested enough to finish it up. After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death. That is a bit extreme IMO. While I agree that it is annoying that the compiler is delayed it is by no means catastrophic. Just download a nightly if you really need a patched version. Otherwise, nothing has really changed on your end and nobody is going anywhere. Things like this happen all the time in volunteer only projects. | |||
4 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Lance Bachmeier | On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier 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? We're nearing four months since missing the deadline for a release, and there's still no announcement from the leadership, and there's apparently nobody available/interested enough to finish it up. After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death. I think Julia just have more active and bigger community and ecosystem | |||
4 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Lance Bachmeier | On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier wrote: >On Monday, 19 August 2024 at 12:59:34 UTC, Quirin Schroll wrote: After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death. Do you need a hug? | |||
4 days ago Re: Why isn’t 2.110 published? | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to claptrap | On 17.11.2024 14:00, claptrap wrote:
> On Saturday, 16 November 2024 at 22:39:34 UTC, Lance Bachmeier wrote:
>> On Monday, 19 August 2024 at 12:59:34 UTC, Quirin Schroll wrote:
>>
>> After more than a decade and hundreds of thousands of lines of code, I've started moving some of my projects to a new language. This only happens to projects that are close to death.
>
> Do you need a hug?
Brilliant answer! My kudos to you.
| |||
Permalink
Reply
