I thought I'd take a minute to go a little more in depth on our recent announcement of 'experimental' builds of CrossOver.In reality the best way to support Wine is to purchase a copy of CrossOver for Games or Productivity applications. Personally, I look at a purchase as a small investment in the future of Wine and CrossOver. A small investment made today can go a long way in insuring the future of our favorite open source application.
It is a very exciting time for Wine - we've been making great strides on our way to Wine 1.0, and I'm thrilled with that progress. But sometimes we struggle with the success and progress of Wine. We'll get customers that come to us and say "CrossOver stinks, Wine runs my application much better." And what can be deeply frustrating is that often Wine will run their application because of our work. This has long been a struggle for us; while we do a lot of the active development on Wine, we take a lot of time to refine that and polish it so that it works reliably before we ship a CrossOver release. Sometimes that makes people complain that CrossOver is old and dull when compared to Wine.
Of course, if you've ever done technical support, you know that dull is good.
But many of our customers don't want dull. They want latest and greatest, the more bleeding edge, the better. And since we're often doing the bleeding edge work, it can be frustrating not to be able to give our customers our very latest work.
So now we have a facility that lets our developers take control. Any developer can now request of our QA lead to have a development build 'blessed'. If the QA lead does a modicum of testing, and feels that it is good enough, then we'll put the build up. That should hopefully speed up the process of making experimental builds available, and allow our developers to more directly interact with our customers.
Friday, May 2, 2008
CrossOver keeping up with Wine
While browsing CodeWeavers site today I came across this post by Jeremy White, the founder and CEO of CodeWeavers.