>> In line with that, complaining loudly and repeatedly to them would seem to >> be the best approach, no?<<
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. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Abbott Sent: Wednesday, January 30, 2008 09:59 AM To: [EMAIL PROTECTED] Subject: Re: Sedna Released ("with this the last Microsoft release ofVisualFoxPro") Hi Rick Rick Schummer wrote: >>> As a matter of interest, have you or anyone you know actually asked > Milind Lele or YAG if/when there'll be another sp?<< > > I learned a long time ago that complaining by itself does no good. The proper > approach is to present > the problem and potential solutions. Yes, I am unhappy with the results of > SP2 too, but instead of > moaning a groaning I am looking to do something about it. I think the key is > to build the business > case for SP3 Unless I'm missing something, the only business case I can think of (looking at it from MS' perspective) is that if they don't put out a new SP it will a) siginficantly damage their reputation in the community generally, that they've fought so hard to recover after the nadir of 10 years ago and b) following on from that, increasing numbers will go down the Open Source route rather than .Net. In line with that, complaining loudly and repeatedly to them would seem to be the best approach, no? and figure out a way Microsoft can put out a service pack that will be adopted by the > Fox Community. I think the way the community feels at the moment, an SP that fixes the small handful of major bugs without introducing any more would be welcomed with open arms. Even if we (or the MVPs) had to do their testing for them, it would still be better than at present. -- Cheers ============ Brian Abbott ============ [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
