Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The issue has already been closed as Fixed.


Based on my experience with connect that doesn't mean it was fixed in the product version you reported it against or any future version.


They mention future version of 2013. So its gone to their bug reports database, to be prioritized rather than is fixed.


From the description of the resolution reasons, that'd be "Deferred".


I'd imagine deferred, is less "pre-grooming" as "nice-to-have-some-time". But I dont work for MS.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: