You forgot this part

dabigkahuna: dabigkahuna: my obviously brilliant compromise idea that no one could possibly disagree with?

More seriously, I think you missed my point because my compromise would be unaffected by all these different things you refer to that came up today. Oh, we’d love to hear about them, but let me give you a counter example to clarify, using the matter of the BT issues which Apple made some improvements to.

First, we’ll assume those BT issues were a gating issue (either Apple has to fix it or you have to have at least have to make it better at your end or you simply won’t ship). You never said it was a gating issue but for this example we’ll assume it was. So, first, you tell us that.

Now we have this ONE issue to focus on, no matter what else comes up or is solved.

Second step is one you already did when you reported that Apple had made some changes which helped. And you did it again when you added that it solved half the issues you reported. And you did it again when you said further improvements from Apple may make it “fully resolved” (which you can confirm later if it is). This is really good stuff to hear! Which brings us to step 3:

Are those improvements, even if you hope for more for that item, good enough to remove it from the gating issue category. If so, then you let us know and we get a new gating issue. If not, you tell us that and maybe give some idea of how close you think you are (or not). For example, you might say, “Apple fixed half our reported problems but we want to eliminate at least half of those remaining before taking it off the list”.

Next, look at your first example above. Under my plan, you may not say anything about it. If you do, it’s a nice bonus. You just focus the one item (or more if YOU want) that is on the table. Doesn’t matter what else is happening. But feel free to give more. We certainly don’t expect to hear what happened each day!

Having at least one known gating issue being addressed here regularly (not every day!) is simply better for us than the alternative of not having any definite gating issues to follow. Heck, I bet most people, if you solve one, will understand if something happens new that puts it back on the table.

In a way, this isn’t different than when we had hardware issues that required physical changes to the keyboard or in how the assembly process was done. They were definitely gating issues, but we could see progress in those areas. It was a big deal when you made a change and things seemed better, but it meant even more when positive reports came in weeks and later months after something was hopefully fixed. Any fix could turn out not to really fix things. But when the longer they hold up, the more likely those problems truly are gone.

So, pretty much the same thing with this firmware stuff.

I see @hrishi1379 wants 3 major issues

But I’ll stick with my request for 1 since it can’t go lower and exist at all. Of course, more is what everyone would want, but I’d be happy with just a small step.

But he is correct about the “kind” of stuff you would include or leave out. Such as the dongle thing. You are just looking into that, after not having the problem before. Way to soon to make it a focus on the forums (unless you want to anyway). The repetitive problems are what we mostly want to know about, like the Apple BT issue. Much like my “problem list” on Slack. I don’t list someone’s problem if it just happened once or incidences are so far apart that we hardly notice them in normal work. Only if the person sees it repeatedly, even if somewhat rare.

Perhaps someday I’ll include the really isolated stuff, but only when there are no bigger ones to worry about.

I do want to second his appreciation that you have been posting a lot more and giving out details here and there more than we usually were getting and you’ve been doing this for 2 months! Good stuff! But I don’t recall anything specifically referred to as a gating issue yet.