Rick
I've got to say I'm dismayed by the "outrage". I've held off going to
SP2 because so much ado was made of it's problems. Well I just
upgraded to it and released a new build of my Visual MaxFrame
Professional based application with the only glitch being a lack of
tooltips in the grid headers. That is a feature none of the users care
about.
So all in all, I'm reasonable happy with SP2.
> No, this would be presenting Microsoft with a threat model. I don't think we need to do this,
> because Microsoft knows the competition better than most companies do. The business approach I am
> suggesting is to identify the killer regression bugs introduced in SP2 that do not have reasonable
> workarounds. Then determine the use cases where the identified bugs are a show stopper with respect
> to adoption. If we can show the limited list of bugs, the reasons why VFP developers can't use the
> product, and how we are minimizing the impact to Microsoft to fix these, then maybe Microsoft can be
> convinced to deliver SP3.
>
> We also have to present the case to show how the community will participate in testing. I personally
> do not think the community really tested SP2 because Microsoft did not hold a formal beta, and those
> who reported issues never received any feedback that the issues were being looked at and fixed if
> appropriate. This combination turned a lot of people off, and now we have to live with the results,
> which stinks.
>
Mike Yearwood
©2008 Mike yearwood |
