Quoting Gavin Dimmock <[EMAIL PROTECTED]>: I believe that Gavin sums it up pretty well here as to why so many of us are requesting a Fix-only release as part of the process:
> My concerns stem from the frustration at getting RB to things it is > supposed to do. As a programmer I want to be spending my time solving > my clients issues, and writing software that helps them do what they > have to do. I do not want to spend my time trying to work out a way > to solve RBs issues, particularly rudimentary stuff. There's nothing more frustrating to either a profession or hobbyiest developer than to have a project run fine in one release of the development tool, but fail in unexpected and difficult to trace ways (especially when the tracing tool introduces a few issuses of its own) in the next version of that same tool. > I'll wait for R3. I have too much time and effort invested in RB to > even entertain the thought of changing back to environments or > consider looking for something new. And that is the issue that many of us face. However, we all can't afford to say - "Aww shucks, RB has some new bugs and so I can't release my updated project (that depends on a fix that DID get into the new version) until the next quick release. I'll just rewrite everything in C++/QT until they fix it." If we have to change platforms, we're probably gone for good. As any business owner/manager knows, it's always easier to gain recurring revenue from existing, satisfied customers than it is to gain a new customer. If the newly introduced bugs drive away the existing customer base, there's a huge potential for loss of recurring subscription revenue that needs to be compared against the potential revenue that a new user would bring because of the new feature being introduced this quarter instead of next quarter. Tim -- Tim Jones [EMAIL PROTECTED] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
