Sorry, I understand some, but not all the aspects of some of the bugs discussed. In the specific mac80211 example I thought it was easily identifiable, but i misunderstood, and admittedly far outside my knowledge base. I understood it to be a pretty big performance drop, thus why i thought it might merit documenting. I didn't want someone to get a bad experience if they are flashing for the first time. I try to always read the known issues in various software docs before using, and i wasn't sure if it is supposed to get updated. The known issues at the top of this thread or at the link to openwrt website for this release only lists 2 issues, which didn't sound like show stoppers but are documented. It was an idea. And maybe i shouldn't be mixing the words "bug" and "issue" together. So I might misunderstand what gets documented as a known issue, when, and if it should continue to be updated. I appreciate all the work everyone does. I was asking the question with the idea most of the people here know a lot more than me. 
so i figured i'd ask. The current documentation is very good and impressive. Thank you for everything.
but you didn't answer the most important question of them all.
how to decide what is a showstopper, or what is the priority.
a 50% decrease in speed for you is a showstopper, while for me I probably wouldn't have noticed if it wasn't pointed out and I didn't do the measurements.
I would consider a device bricking a major issue. But even a network adapter not starting could be debatable if you talk about performance. Maybe for me I can live without, while others can't.
the priority is really situation specific.
Example: if there is a critical issue in windows which only applies to a few people changes are you have to wait 6 months for a fix, and then this is a company where people actually get paid for the development.
So I really think, the developers do the best they can do. and if there is an issue, there are several possibilities for you, revert/wait/snapshot but the priority I think should be up to the developers as they also do al the work.
@eginnc Could you please summarize your message in relation to the mac80211 bug you quoted? I read your message multiple times but do not understand the relation to the issue. Thanks.
I read that others have the issue, repeatedly checked my device and was suprised that I could not reproduce it. Because of this I would mention the affected devices in a bug report.
For example: devices brick after installing the update or basic routing, firewall, wifi or switch capabilities from the default sysupgrade image stop working after the update. This would be a showstopper for me.
I expressed a lengthy opinion that instead of a bug report, there could just be a new point release. It's already been fixed in PR 16007, implemented in the very first 23.05 snapshot commit within a week of 23.05.4 being branched.
In a stable OS release intended to provide WiFi functionality, a bug that halves 2.4 GHz WiFi throughput is a showstopper in my opinion, in that I don't think such a bug should persist in a stable release without prompt correction in a new point release. I don't think a bug needs to be so serious it bricks devices to merit prompt correction in stable. Bugs like this are to be expected in main snapshot, but not stable point releases. Others may disagree of course.
And it may not even be halved but quartered. I have no way to quantify it now, since I don't have a "before" way to test, but it seemed much worse than halved. Either way, something like this should have been added to the release notes within a day or two of its discovery.
What is the percentage of devices impacted by the bug?
The fix is already merged in 23.05 branch. The 23.05-snapshot sysupgrade images including the fix are available for download. I posted the links to them here. Please test the fix and share your test results if you are affected.
The 23.05-snapshot image for Belkin RT3200 fixed the wifi download throughput problem I reported earlier.
No harm in more data I suppose, if that is what you are after. However, it is already very clear from the replies in the PR for the fix and in this thread that the problem was real, it had a significant impact, it was experienced by several users, and the fix corrects the problem.
I'll wait for the next stable point release myself. I maintain a router for another and do not want to install 23.05 snapshot on it, because when the 23.05 snapshot kernel next updates it will break package compatibility.
It's too bad that the 23.05-snapshot is not available with the online firmware selector 
Yes, it is. The list drop down menu has SNAPSHOT above the default selection.
Your browser may hide this as the list is long, but just scroll up.
AFAIK, the SNAPSHOT is for the next release (24.xx.xx) not the next 23.xx.xx.
As @clauded said, the SNAPSHOT in the Firmware selector is the next release of OpenWRT with newer packages, kernel 6.x and so on. On my RT3200 I would need to run a new installer or that release would brick it.
23.05-SNAPSHOT is not available. Only on the downloads page with default packages. Not possible to customize it like on Firmware Selector.
Cheers!
Is there a thread discussing the next release and what we can expect of it?
Not that I'm aware of.
I just hope we get 23.05.5 soon.
You can use the imagebuilder found on that downloads page. I've been using the imagebuilder for 23.05-SNAPSHOT for a couple of weeks now with no unexpected problems.
Has anyone installed the new release on the FriendlyElec Nanopi R4S? Did ot go ok?
I installed on R4S without issues. Why you ask?
After all said here I am skipping this release. Thanks work and kids for keeping me busy and making me don't update on day one.
I suggest anyone still on 23.05.3 to do the same
I'm guessing that anyone who's been hit with issues can just use their last good image and settings backup to roll back to what was already phenomenal router software? I was also lucky in that kids and work stopped me from getting round to updating as soon as I wanted.
Maybe it's my paranoia taking over, but this made me think of a bigger issue that arose elsewhere in FOSS a while back - Hackers using pressure to do bad stuff
As always thanks to the Devs and the enthusiasts who make this stuff work, you guys are legends.
Ps. Any news on when 24.x might be heading our way?
Ta. Happy