4 ms·
It was in the release candidate. It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first releas
by tumult 3y ago
It was in the release candidate.
It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first release candidate. This is covered in the article.
- crazygringo 3y agoBut regardless, obivously none of us here have the slightest idea whether it was in the pipeline to be fixed anyways, or if it was because of HN. It might have been HN, but it might not have been. (Surely other things have been fixed between RC and release without HN intervening.)
- tumult 3y agoRelease candidate means it could have gone out as a release. RC2 ended up being the release version.