Skip to content

Conversation

@dkorpel
Copy link
Contributor

@dkorpel dkorpel commented Aug 14, 2025

No description provided.

@dlang-bot
Copy link
Contributor

Thanks for your pull request and interest in making D better, @dkorpel! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

  • My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
  • My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
  • I have provided a detailed rationale explaining my changes
  • New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.


If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

@dkorpel
Copy link
Contributor Author

dkorpel commented Aug 14, 2025

afbeelding Mmm, the padding looks off

@adamdruppe
Copy link
Contributor

adamdruppe commented Aug 14, 2025

In June, I wrote an email to the local city council saying the new speed bumps at the park are unnecessarily dangerous to cyclists and suggested they act to correct the problem before somebody got hurt. Correction could be as easy as shortening them; it could have been done same-day.

They did nothing. Not even a full month later, in July, one person was injured and another killed in a crash in that exact location, almost certainly caused by those bumps.

A week later, when the news published a copy of my email, the city decided to add a "SPEED BUMP AHEAD" sign to the road. The council, later that night, went into executive session to discuss current, pending, or potential litigation. The dangerous bump remains unaltered, waiting for its next victim.

@dkorpel
Copy link
Contributor Author

dkorpel commented Aug 14, 2025

I really want to release 2.111.1 or 2.112.0 yesterday, but the current release process is so complex, rigid and fragile that is's really hard to get something going while errors keep popping up at every step. I hope to find some help this DConf to sort it out.

@dkorpel dkorpel force-pushed the apply-nightly-downloadlink branch from 4176888 to 965edf5 Compare August 14, 2025 21:46
@dkorpel dkorpel merged commit f57d363 into dlang:master Aug 15, 2025
2 checks passed
@schveiguy
Copy link
Member

I hope to find some help this DConf to sort it out.

Let's make it a priority for hackathon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants