They add a message asking us to send them an email with the FDBK code, so they keep track of the issue!
At first glance, this looks as a very silly way of using your bug/suggestion tracking system. Why not just postpone the review for the next iteration and keep it in the database?
Why do you need to clean up the bugdatabase?
Is it a law at Microsoft that the database must be emptied of pending (no matter pending for when) items before RTM, or what?
Life, software, politics, arts, and naive future prediction (This blog is in suspended animation)
Subscribe to:
Post Comments (Atom)
Moving to MSDN
I haven't decided yet, but it is very likely that I will stop blogging here for some time. For some background, I have moved to the sate...
-
Mats Helander apparently explores the same subject of "composable data services" in his post , although he seems to arrive from a ...
-
UPDATE 3/1/2006: The hotfix is officialy out for the Visual Basic background compiler crash. Thanks to Lisa, Margaret, and the VB Team. UP...
No comments:
Post a Comment