"And all the update definitely do happen before the promised date."
Just to get it out there up front -- this is meant in a constructive manner, but I'm not so good at articulating things clearly sometimes. My apologies in advance if it comes across wrong. This isn't particularly focused on this thread; I've observed this happening on a lot of drops, and I'm hoping I can provide some useful data.
In many of these types of comment threads, it feels like we've all been talking past each other. I don't think anybody is particularly irritated, but here's what I see going on: The impression given by promising an update "on <date> or sooner" is that the update MIGHT come early. The dissonance comes, in my limited experience, from the fact that drop updates that are early are an expectation, but when they're met at the last minute, it somehow feels like a violation of that expectation.
Human psychology being what it is, even when updates come early, if there's one that somehow feels like it's late (even though it's technically not), that one psuedo-late update taints the whole thing.
Let's take the update post on this very drop as an example. An update was promised "on 1/15 or sooner." The expectation is that the update might get here early, 1/15 at the latest. The update was provided on 1/15 -- at 11:48 PM. I'm in the same time zone. I was actually up when it came in.
12 minutes left in the day. Yes, that meets the letter of what was promised, but even though you're doing exactly what you promised, it doesn't *feel* like it.
The only solution I've been able to come up with is to instead say, "Expect an update at the end of the day (PST) on 1/15." That way, if you're early, we're all delighted, but if it comes in at 11:48 PM, we're not disappointed.
Does that make sense / help?