IMHO seeing Wine move to a release level beyond
alpha would help sell it to developers, especially
commercial ones, as a viable way to port Windows
applications to Linux/Unix. My only warning would be
not set set false expections, i.e. give the impression
that Wine 1.0 will run *all* Windows applications
"out of the box".

One of the things we want to do after our current
project is completed, is to start pushing changes
we've made in Corel Wine out to WineHQ and merge
the changes in WineHQ wine with our version (as
much as possible).

I'd also like to see some kind of roadmap as to
what will be in Wine 1.1, 1.2, 2.0, etc.

Should we start thinking about having stable and
development branches of Wine?

Jeremy White wrote:
> 
> Given the amount of progress Wine has made over the past year,
> it seems (to me anyway) that the time may be appropriate to
> try for Wine version 1.0.
> 
> I was hoping to spark a conversation on this topic, in two basic areas:
>     1.  Should we do it?  (If not, why not, and when?)
>     2.  What needs to be done before we can release Wine 1.0?
> 
> I'll start with my personal list:
>     1.  All apps listed as a '5' work perfectly with Wine
>         (revising the apps database so that it's accurate
>          is a fine way to accomplish this, IMO).
>     2.  Many sample applications compile and work with Winelib 'out of
>         the box' (along the lines of the work that Francois Gouget is doing).
>     3.  The installation and configuration stuff is cleaner
>         (I think it's mostly there; I just think it needs a
>          little spit and polish).
>     4.  The wine server interface is standardized so that
>         Wine version 1.01 and version 1.1 and version 2.0
>         will be able to interoperate with the Wine 1.0 server.
> 
> Thoughts?  Comments?
> 
> Jeremy

-- 
Jeff Tranter  Project Leader, Linux Development (Wine team), Corel Corporation
Take your office suite performance to an exciting new level. Check it
out at http://www.corel.com/featuresinaction
-- 
The address in the headers is not the poster's real email address.  Do not send
private mail to the poster using your mailer's "reply" feature.  CC's of mail 
to mailing lists are OK.  Problem reports to "[EMAIL PROTECTED]".  
The poster's email address is "[EMAIL PROTECTED]".

Reply via email to