Okay @WayTools, time to really focus in on my pet peeve. Addressed it here and there before, but it really is something that needs correcting.
We’ve all seen posts from many people about how you should do things. Some may be right or wrong (like whether you should ship the old version).
Some are a bit silly, based on nothing more than people want the device they ordered - nothing silly about wanting it, but sometimes that ignores other issues.
No, my point is the simple, basic logic that when YOU say something, it is appropriate for you to act accordingly.
Many people will want updates, for example. You can choose not to give them. Everyone then makes their own decision about what to do based on the lack of the updates they want. While I would not agree to a lack of updates, that is your decision, for better or worse.
But here is the problem that I don’t think you can defend: YOU set a date (specific, or fairly narrow) to provide info. No one can make you do that, no matter how much they complain. So, your choice.
At that point, the “how things are done” has only one real answer - you do what YOU decided to say you would do.
Sure, you may say something will happen by a certain date and have something come up. That’s the same thing as someone coming to work on time, but one day they get delayed by a major accident blocking traffic.
But that is RARE. People accept such failures to be on time BECAUSE they are rare and out of your control.
Unfortunately, this has NOT been “rare”. We can go back to June 2018 for a big update, which still hasn’t happened.
We can go back to Summer of 2019 when the update only required ONE MORE DAY. Actually, that was said two days in a row! Yet that big update isn’t here yet.
And we can go back to February 10th when you said more information on a specific subject would be coming around the end of the month. And before someone says, “they didn’t say which month”, I’m more aware than most at how timeframes given are not as restrictive as some claim. In this case, the context clearly meant around the end of February.
But, here we are at the end of March and it still hasn’t been posted.
There is no way I can imagine you can’t do what YOU said you would do. Especially when it keeps happening. Like I said, I can at least understand not offering anything. I can NOT understand offering something and then not doing it anyway.
I try imagining possible legal reasons - but that doesn’t work because you would know those when you say you will provide information.
I try imagining some tech problem coming up taking all your time - but that can’t explain these things happening not only over and over, but not being done at some point soon afterwards, especially when you say you will give some other update, which also doesn’t happen. And certainly not when you only need ONE more day!
I remember when you would do updates and some of the crazier critics would use the updates to attack. But, first, they aren’t here anymore and, second, when you said you would update, you already knew about that kind of reaction. So it can’t be used to explain not giving the update you said we would get.
So, speaking for myself, I’m just after you to do what you CHOSE to say you would do about updates. Release can be affected by lots of things and treggers are well aware of how often new problems were discovered (though we hope that is over). But an update? Even a tech issue is, ultimately, just an opportunity to give us some idea of what is going on!
A reminder of the last time you said we would get more info:
Somewhat tedious process to go through the migration and detailed merge reports, but the compiler tools are actually pretty good at identifying even subtle potential contentions. So new tools are quite productive, and make new code that is pretty rad-hard.
Will have more visibility on remaining tasks around end of month.