More generally, from a core dev perspective, this completely breaks trust. Our job is already hard enough, and we already have trouble recruiting. If on top of this we have to offer a white glove service to people who don’t take the time to participate to critical discussions, but still feel entitled to create a controversy, we might as well already stop, I can tell you it’s not worth it for anyone with our skillset, at any price point.
I think anyone is entitled to create a controversy, like you here with your post.
From engineer point of view this is bad take, users (holders&bakers in this case), more than usual don’t read documentations, don’t follow procedures and I understand that this cause frustration, believe me as a developer, I know how it feels.
But, I need to remind you that part of devs job (or project manager if any) is to know how to communicate changes, communication (like respect) is a two-way street, is a failures from everyone, there is no point to create a controversy of a controversy to shame the other group, we are all together on this. Also, assuming a failure remind us that we are human, and make us humble, a necessary thing to have good relationship and sane debate.
I’ve the major of respect for core devs, more in these environment, at the same time nobody here is forced to continue so I guess they are doing it because they feel is important, has future and economically makes sense.
So, I’ll recommend to learn from this experience, do a blameless post-mortem, and try to mitigate the same problem in the future.
