Quote Originally Posted by AmiableApkallu View Post
I work in software development, too, so I'll bite: What's the point in insisting on synchronized announcements here? No one's put at any sort of real advantage or disadvantage based on hearing the news a couple hours sooner or later (we're past the world-first clears). There's nothing for the players to do but wait for the fix to rollout. If it weren't for the modern Internet reducing everyone's patience to zero, we wouldn't even be talking about this.

Give them a knock for not acknowledging the bug earlier than they did. :P
It gives the side that hears about it later the impression that they don't matter as much. I work for a laboratory with both NA and international locations and when our customer-facing application is down we make sure the announcement is created, translated by our team into our available languages, and then posted for all our customers to see at once. It's just a courtesy thing but courtesy is still important if you want to look good to your customers. If you're just on the development side then it may not be something you touch but I'm both development and customer interaction so it's definitely something on my radar.

I don't give them as much of a knock for not acknowledging the bug sooner because they were probably still in the investigation and replicate phase. I've certainly run into bugs that took longer than others to identify as a bug.