www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Please release me

reply please-release-me <releaseme gmail.com> writes:
D v2.100.1 (released Jul 15, 2022)

today is 15 August.

still, cannot download v2.100.1.

I don't know the reason.

All I can say, is that it looks pretty poor.
Aug 14 2022
next sibling parent matheus <matheus gmail.com> writes:
On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me 
wrote:
 D v2.100.1 (released Jul 15, 2022)

 today is 15 August.

 still, cannot download v2.100.1.

 I don't know the reason.

 All I can say, is that it looks pretty poor.
It could be time zone? Matheus.
Aug 15 2022
prev sibling parent reply Dennis <dkorpel gmail.com> writes:
On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me 
wrote:
 All I can say, is that it looks pretty poor.
It does.
 I don't know the reason.
The release process is being updated, but there are a few snags. If you want the newest updates sooner, you can check out the nightly build on GitHub: https://github.com/dlang/dmd/releases/tag/nightly
Aug 15 2022
next sibling parent reply M.M. <matus email.cz> writes:
On Monday, 15 August 2022 at 13:17:33 UTC, Dennis wrote:
 On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me 
 wrote:
 All I can say, is that it looks pretty poor.
It does.
 I don't know the reason.
The release process is being updated, but there are a few snags. If you want the newest updates sooner, you can check out the nightly build on GitHub: https://github.com/dlang/dmd/releases/tag/nightly
I would find it a nice read to know the background on the "release process is being updated" changes in the dlang ecosystem. Was it announced somewhere on the forum (and I missed it somehow)?
Aug 16 2022
next sibling parent reply bauss <jacobbauss gmail.com> writes:
On Tuesday, 16 August 2022 at 12:34:01 UTC, M.M. wrote:
 On Monday, 15 August 2022 at 13:17:33 UTC, Dennis wrote:
 On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me 
 wrote:
 All I can say, is that it looks pretty poor.
It does.
 I don't know the reason.
The release process is being updated, but there are a few snags. If you want the newest updates sooner, you can check out the nightly build on GitHub: https://github.com/dlang/dmd/releases/tag/nightly
I would find it a nice read to know the background on the "release process is being updated" changes in the dlang ecosystem. Was it announced somewhere on the forum (and I missed it somehow)?
It's just the usual "someone trying something new that doesn't work initially and breaks it for everyone else" concept, only found within D. It's a feature at this point that someone just decides to do something new without any real feedback, testing or critical thinking done beforehand. The fact this has been ongoing for so long is almost embarrassing.
Aug 16 2022
parent Steven Schveighoffer <schveiguy gmail.com> writes:
On 8/16/22 8:44 AM, bauss wrote:
 On Tuesday, 16 August 2022 at 12:34:01 UTC, M.M. wrote:
 On Monday, 15 August 2022 at 13:17:33 UTC, Dennis wrote:
 On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me wrote:
 All I can say, is that it looks pretty poor.
It does.
 I don't know the reason.
The release process is being updated, but there are a few snags. If you want the newest updates sooner, you can check out the nightly build on GitHub: https://github.com/dlang/dmd/releases/tag/nightly
I would find it a nice read to know the background on the "release process is being updated" changes in the dlang ecosystem. Was it announced somewhere on the forum (and I missed it somehow)?
It's just the usual "someone trying something new that doesn't work initially and breaks it for everyone else" concept, only found within D.
No, it's not. Someone who registered the official servers/certificates is no longer active in the community, and those registrations expired. They are working on setting up a more robust system. -Steve
Aug 16 2022
prev sibling parent Dennis <dkorpel gmail.com> writes:
On Tuesday, 16 August 2022 at 12:34:01 UTC, M.M. wrote:
 I would find it a nice read to know the background on the 
 "release process is being updated" changes in the dlang 
 ecosystem. Was it announced somewhere on the forum (and I 
 missed it somehow)?
It's been discussed in Foundation meetings, which have summaries posted on the Announce board, e.g.: https://forum.dlang.org/post/zfmkiqwkkexeaohjsuru forum.dlang.org
 I gave an update on the status of our plans to bring all of the 
 ecosystem services under our control.
https://forum.dlang.org/post/ntnxtskafgoalcramqry forum.dlang.org
 Iain went through the release process with Martin Nowak so that 
 he could learn how it's done. He didn't yet have the secrets to 
 upload to the S3 servers, but he was planning to upload the 
 2.100.0 beta once he got them (and that was announced on April 
 22).
There's been a problem with single volunteers being responsible for maintaining critical ecosystem services, and we're trying to step away from that by giving more people access to these services.
Aug 16 2022
prev sibling parent reply linger <xiao linger.me> writes:
On Monday, 15 August 2022 at 13:17:33 UTC, Dennis wrote:
 On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me 
 wrote:
 If you want the newest updates sooner, you can check out the 
 nightly build on GitHub:

 https://github.com/dlang/dmd/releases/tag/nightly
if github nightly is usable, why not just upload release to github? like LDC did.
Aug 16 2022
parent max haughton <maxhaton gmail.com> writes:
On Wednesday, 17 August 2022 at 03:25:16 UTC, linger wrote:
 On Monday, 15 August 2022 at 13:17:33 UTC, Dennis wrote:
 On Monday, 15 August 2022 at 00:30:13 UTC, please-release-me 
 wrote:
 If you want the newest updates sooner, you can check out the 
 nightly build on GitHub:

 https://github.com/dlang/dmd/releases/tag/nightly
if github nightly is usable, why not just upload release to github? like LDC did.
We've basically sorted out where to host the release, they're currently being transferred as I write this, the thing that's really blocked this is that the human side of releasing a D release has changed *and* how the cryptographic signing is done is changing too. This requires spending money so progress hasn't been as fast as it necessarily should've been. Personally I think we should use Github releases for more things but that side is done now.
Aug 17 2022