Part of the issue here is that someone has to step up to make those announcements. Who is going to monitor the channels constantly, and release info? Do you really think it's the best use of a developer's time to have them stop coding, flush their mental buffers, and post a status update daily?
Marcos posted weekly. Play by Play, minute by minute communication takes a dedicated communications resource. All GRC has right now are random people deciding to make posts here or there. Sometimes someone makes posts for several months at a time, and then they stop.
Consider what it would take to make you personally commit to that effort, long term. It's likely, that is a starting point for making it happen. Right now operations is pinned posts in slack. Does all of that need to be on the public wiki? Does there need to be a team of communicators? How do you authenticate that they are truly communicating on behalf of GRC?
The most simple things are often the most complicated to make happen.
Lately I've been trying to communicate the dev's work to the community more effectively in my new position. Let me know how I can improve. Current plans are weekly or every other week postings about dev happenings (unless there is an update that week which takes priority).
Yes, indeed, I thought the same. There is no reliability and that is bad.
This is not the "fault" of the volunteers, it is just how things work in a crowd of volunteers with no strict goals.