[mmr] Re: some new email tracking mechanism?
- From: "Julian Koh" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "kohster" for DMARC)
- To: mmr@xxxxxxxxxxxxx
- Date: Mon, 21 Oct 2019 21:24:05 -0500
On Oct 8, 2019, at 12:02, Julian Y. Koh (Redacted sender "kohster" for DMARC)
On Oct 8, 2019, at 11:30, Julian Koh (Redacted sender "kohster" for DMARC)
<dmarc-noreply@xxxxxxxxxxxxx <mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
Filed developer feedback item #FB7359396
Also sent a sternly worded note to product-security@xxxxxxxxx
<mailto:product-security@xxxxxxxxx>. Odds on receiving response?
Heh. From today’s TidBITS at
Regressions Get Fixed. Old Bugs Get Ignored.
Apple is lousy at fixing old bugs.
Apple pays special attention to new products like the iPhone 11, looking for
serious customer problems. It jumps on them quickly and generally does a good
job of eradicating major issues. But any bugs that are minor or unusual enough
to survive this early scrutiny may persist forever.
Remember what I said about changes causing new bugs? If an engineer
accidentally breaks a working feature, that’s called a regression. They’re
expected to fix it.
But if you file a bug report, and the QA engineer determines that bug also
exists in previous releases of the software, it’s marked “not a regression.” By
definition, it’s not a new bug, it’s an old bug. Chances are, no one will ever
be assigned to fix it.
Not all groups at Apple work this way, but many do. It drove me crazy. One
group I knew at Apple even made “Not a Regression” T-shirts. If a bug isn’t a
regression, they don’t have to fix it. That’s why the iCloud photo upload bug
and the contact syncing bug I mentioned above may never be fixed.
Other related posts: