Sooo quiet...

[Eric Pouech]

> ... I feel like starting a flamewar, just to get some
> traffic on this list :)
that's true... we really miss some good ones (licence issues, 
regression test suite...) ;-)

> Wine's been around for 8 (_eight_) years (how time flies)! It is my
> understanding that we're approaching the 1.0 status. I say, let's change
> the versioning scheme, just to give the outside world a feeling of
> progress. Really, I think the current scheme kindda hurts us on a PR
> level.
> 
> We can start with something like 0.90.0. This should give us plenty
> numbers to the upcoming 1.0, don't you think?
IMO, what's important behind version numbers isn't the version in
itself, 
but rather:
1] the goal you want to reach
2] the milestones between where you stand and 1]

speaking on 1], it's has been discussed a bit before, but no clear
definition has been put up.
you can either describe Wine 1.0 in terms of:
a) what should Wine 1.0 do? in other words, which apps to you want
   it to run?
b) what should Wine 1.0 be able to do? in other words, the functions
   you want to be implemented.
this functional vs technical controversy isn't new.

Some folks were more interested in the a) approach. It's what
Transgaming did (does) with a target on games (as applications). Some
others may suggest (O|o)ffice applications (it seems CodeWeavers folks
have been busy on this matter lately ;-)

Some other (including Alexandre) were more in favor of the technical 
approach. This would include finishing the major hurdles. IIRC the
discussion at that time, I think most of them have been removed 
- address space separation: mostly done (even if some USER issues still
  need to be debugged)
- window management rewrite: still in progress
- TrueType handling: at least done with Huw latest patches and using
  XRender (on Xfree >= 4.0.0)
Alexandre biggest argument at that time was to stabilize the wineserver
protocol definition, so we could upgrade user's side component in a
rather stable manner.

Anyway, on a more pragmatic term, let's see what needs to be done:
from the a) view:
- let most of the installers work. This would require some OLE tweaking.
  Transgaming has part of it, but isn't ready yet for submission

from the b) view:
- stabilize the wineserver protocol (there's still a few pending issues
  to be added).
- put up a decent regression test in place (framework AND tests)
- Unicode support (wide, has to be precised a bit)
- finish the window management issues
- let the documentation be in sync with the code
- fix a guzillion bugs

A+

-- 
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle