Cherry-picking commits to stable: 17650 + CODEOWNERS

[wilzbach]

#5612 should have been targeted at stable.

Also at #5614 I realized the CODEOWNERS file isn't part of stable and will take quite a long time to get be merged back into stable again, so I cherry-picked this as well while I was at it.

Note that due to the GH bugs in the CODEOWNERS implementation it took us three PRS to achieve a working CODEOWNERS file.

[dlang-bot]

Thanks for your pull request, @wilzbach!

Bugzilla references

Auto-close	Bugzilla	Description
✓	17650	[REG v2.075.0 b1-b4] std.getopt range violation

[JackStouffer]

Ping @MartinNowak. Might have to delay the release again.

[wilzbach]

Ping @MartinNowak. Might have to delay the release again.

FYI:

• in general it's best to ping him on slack
• He is aware of the issue and joined the card on Trello: https://trello.com/c/9P437E6M/334-issue-17650-reg-v20750-b1-b4-stdgetopt-range-violation

I realized that not many people are aware of the boards:

• https://trello.com/b/XoFjxiqG/active
• https://trello.com/b/jGdlx9vZ/backlog

[JackStouffer]

Thanks for the Trello invite @wilzbach

[jondegenhardt]

@wilzbach Thanks for cherry-picking #5612. In the initial response to the bug Martin indicated a preference for waiting until the first point release. I assumed stable would the initial release, not the first point release. However, I should have at least put a note in the PR asking about the issue, and suggesting the fix may be important enough for the initial release.

[CyberShadow]

Seb, why did the bot not show the warning on #5612?

[aG0aep6G]

Seb, why did the bot not show the warning on #5612?

It did originally. I see it in the email. Maybe it removed the warning when merging?

[wilzbach]

Maybe it removed the warning when merging?

Yep :)
But as I also noticed this I merged the pending PR to fix this behavior:

dlang/dlang-bot#121

So the bot shouldn't overwrite his comment in the future after a merge.

[wilzbach]

@wilzbach Thanks for cherry-picking #5612. In the initial response to the bug Martin indicated a preference for waiting until the first point release.

No worries, we/I just try to make stable what it is supposed to be and I think Martin wanted wait for the first point release because he assumed it would take us days to fix this and not a couple of hours with your ultra fast fix 😉
So thanks a lot for finding and fixing this!

[MartinNowak]

Already tagged a release candidate yesterday, so this will be released a week later or so when we've fixed the other open regressions.