(no title)
netruk44 | 3 months ago
These days, the only testing any release of Windows gets is from Microsoft employees (Dev/PM) and Windows Insiders.
They have rules of how many hours of self-hosting are required before they can release, but that’s the only requirement. That there exists telemetry of it running.
You might see a gap with that testing methodology, but it might also explain how things like this happen. If it’s a bug that doesn’t prevent boot, it’s easy to ignore.
(I knew a few devs who would just put builds of windows on one of their computers and play a 72 hour long video of a black screen on repeat to get self hosting hours. Then they would proceed with their feature release. And nobody saw any problem with that.)
sumtechguy|3 months ago
MS is losing the people who cared about using them. Those people are migrating to linux/macos. I dont blame em.
MandieD|3 months ago
We were also, essentially, Apple's Mac OS X post-release testing team (10.0 Cheetah was released while I was there, but I missed the party because my grandmother had died and I was back home for her funeral) - we ran into all sorts of exciting problems with basic OS functions.
One of the things MacBU prided themselves on was having fewer people putting out the whole Office suite PLUS Internet Explorer for Mac than there were working on Word for Windows alone, yet still managing.
rdhatt|3 months ago