• Mike Parker (12/12) Nov 29 I've finally got some news for you on the state of the next
• ryuukk_ (3/15) Nov 29 Thanks for keeping us updated, and i hope everything is fine for
• jmh530 (2/14) Nov 29 Thanks for the update. Wishing Iain the best.
• Richard (Rikki) Andrew Cattermole (17/31) Nov 30 I've been looking into it as well, what I've found is that the nightlies...
• M. M. (4/16) Nov 30 Thank you for the update. The release can wait, but at least the
• claptrap (3/7) Nov 30 That's quite disappointing, I was really quite looking forward to

Mike Parker <aldacron gmail.com> writes:

I've finally got some news for you on the state of the next 
compiler release.

Unfortunately, Iain Buclaw will be unavailable until sometime in 
January at the earliest. We look forward to his return.

In the meantime, he's provided us with some notes on the release 
process. Nicholas Wilson has volunteered to look into it and see 
if he can make it happen. It's a complicated process that only 
Iain knows inside and out, but hopefully we'll be able to get a 
release out in the near future.

Regardless, we'll make it a priority when Iain returns to revamp 
the process such that any one of us can push out a new release. 
Then we can avoid a repeat of this situation.

ryuukk_ <ryuukk.dev gmail.com> writes:

On Friday, 29 November 2024 at 16:01:33 UTC, Mike Parker wrote:
 I've finally got some news for you on the state of the next 
 compiler release.

 Unfortunately, Iain Buclaw will be unavailable until sometime 
 in January at the earliest. We look forward to his return.

 In the meantime, he's provided us with some notes on the 
 release process. Nicholas Wilson has volunteered to look into 
 it and see if he can make it happen. It's a complicated process 
 that only Iain knows inside and out, but hopefully we'll be 
 able to get a release out in the near future.

 Regardless, we'll make it a priority when Iain returns to 
 revamp the process such that any one of us can push out a new 
 release. Then we can avoid a repeat of this situation.

Thanks for keeping us updated, and i hope everything is fine for 
Iain

jmh530 <john.michael.hall gmail.com> writes:

On Friday, 29 November 2024 at 16:01:33 UTC, Mike Parker wrote:
 I've finally got some news for you on the state of the next 
 compiler release.

 Unfortunately, Iain Buclaw will be unavailable until sometime 
 in January at the earliest. We look forward to his return.

 In the meantime, he's provided us with some notes on the 
 release process. Nicholas Wilson has volunteered to look into 
 it and see if he can make it happen. It's a complicated process 
 that only Iain knows inside and out, but hopefully we'll be 
 able to get a release out in the near future.

 Regardless, we'll make it a priority when Iain returns to 
 revamp the process such that any one of us can push out a new 
 release. Then we can avoid a repeat of this situation.

Thanks for the update. Wishing Iain the best.

"Richard (Rikki) Andrew Cattermole" <richard cattermole.co.nz> writes:

On 30/11/2024 5:01 AM, Mike Parker wrote:
 I've finally got some news for you on the state of the next compiler 
 release.
 
 Unfortunately, Iain Buclaw will be unavailable until sometime in January 
 at the earliest. We look forward to his return.

Indeed!

 In the meantime, he's provided us with some notes on the release 
 process. Nicholas Wilson has volunteered to look into it and see if he 
 can make it happen. It's a complicated process that only Iain knows 
 inside and out, but hopefully we'll be able to get a release out in the 
 near future.
 
 Regardless, we'll make it a priority when Iain returns to revamp the 
 process such that any one of us can push out a new release. Then we can 
 avoid a repeat of this situation.

I've been looking into it as well, what I've found is that the nightlies 
are more or less the same as a full release minus say the version string 
and code signing (which we don't do anyway).

 From the building perspective it shouldn't be too difficult to trigger 
for all platforms except for FreeBSD which GH runners don't support.

What I've been experimenting with is the merging of branches via PR with 
automatic creation.

https://github.com/rikkimax/experiment-gh-flow

The existing GH action I am using does have a bug and really isn't 
designed for our workflow of master/stable branches.

Apart from FreeBSD we should be able to replicate it using just bash, 
uploading of artifacts ext. should be non-issues.

My general suspicion is that long term we need our own Linux/Windows + 
OSX runner. If we have this we can also handle code signing with a 
hardware key (which is required these days).

M. M. <matus email.cz> writes:

On Friday, 29 November 2024 at 16:01:33 UTC, Mike Parker wrote:
 I've finally got some news for you on the state of the next 
 compiler release.

 Unfortunately, Iain Buclaw will be unavailable until sometime 
 in January at the earliest. We look forward to his return.

 In the meantime, he's provided us with some notes on the 
 release process. Nicholas Wilson has volunteered to look into 
 it and see if he can make it happen. It's a complicated process 
 that only Iain knows inside and out, but hopefully we'll be 
 able to get a release out in the near future.

 Regardless, we'll make it a priority when Iain returns to 
 revamp the process such that any one of us can push out a new 
 release. Then we can avoid a repeat of this situation.

Thank you for the update. The release can wait, but at least the 
dlang foundation has a clear picture of the situation.

Wishing well to Iain and his soon coming back.

claptrap <clap trap.com> writes:

On Friday, 29 November 2024 at 16:01:33 UTC, Mike Parker wrote:
 I've finally got some news for you on the state of the next 
 compiler release.

 Unfortunately, Iain Buclaw will be unavailable until sometime 
 in January at the earliest. We look forward to his return.

That's quite disappointing, I was really quite looking forward to 
Dlangageddon