[cw-discuss] Rebasing Crossover on current wine?

[Jeremy White]

Hi Carl-Daniel,

Yes, 6.2 is based on a Wine vintage that corresponds roughly to April of this year.

Of course, that includes a fairly substantial number of CrossOver specific
patches as well as many fixes that we've developed through the year.  However,
it does not include the broad range of changes that have gone on in the public WineHQ tree.

Version 7.0 will be based on some future version of Wine; likely
one from November or early December (depending on when we choose to freeze).

Just to be complete, here is the full process:

  *  We do nearly all development against Wine HQ

     So most of our work appears as a patches in the wine-patches mailing list.


  *  Between releases, we keep the CrossOver tree merged with the Wine tree,
     so the CrossOver tree is largely the same as the Wine tree.

     There are differences; our so-called 'proprietary advantage'.  These are patches
     that are hacks or kludges that solve specific problems with our supported applications.
     Essentially, we add work arounds for situations when Alexandre refused to accept them.
     (Alexandre likes to refuse kludges, as he feels it ensures that people will remain motivated to
     submit the correct patch).  And, yes, sometimes our differences are wrong; that is
     why sometimes WineHQ works better than CrossOver.  Generally, though, for our supported
     application list, our patches are best.


  *  At some point, usually about 8 weeks prior to the hoped for release date,
     we 'cool' our tree, so we stop doing complete merges with Wine.

     We start the process of stabilizing the CrossOver tree.  Note that we'll still do
     our work in Wine, fixing issues furiously; the difference is that now we cherry pick
     the patches we want, instead of doing large scale merges.


  *  When we finish that stabilization, we ship

     That's always longer than we originally wanted it to be; that's one of
     those rules of Software Development.


  *  When we ship, we branch


  *  As we find bugs in the new main release, we fix them on the branch

     Those fixes eventually see the light of day in the presumably stable .X releases.

     (Of course, we've broken this rule in the past; 6.1 ended up being a full WineHQ
     merge, instead of a stable update.  See the note about things taking too long,
     above...)


At any rate, I'm sure that's a far longer answer than you wanted.

But you can be sure that 7.0, when it ships, will be a very modern
Wine, polished to reliably run the applications we support.

Cheers,

Jeremy


Carl-Daniel Hailfinger wrote:
> Hi,
> 
> with Crossover 7.0 in the works, can you give an estimate which wine
> version it will be based on? Crossover 6.2 seems to be based on a rather
> old version (probably all of the 6.x branch is based on the same
> version, haven't checked) and current wine supports some applications
> which do not work well under Crossover 6.2.
> 
> It would be nice if Crossover 7.0 stopped tracking Wine only when 7.0rc1
> is released, but maybe your release process is different.
> 
> Regards,
> Carl-Daniel
> 
> 
> _______________________________________________
> discuss mailing list
> discuss at crossover.codeweavers.com
> http://crossover.codeweavers.com/mailman/listinfo/discuss
> You can be removed from this list by visiting the above web page, or by checking the 'subscriptions' tab in your account with CodeWeavers.
>