Release plans

Folks, Now that the Mac driver is fully merged and all the bugs fixed (right?), it's time to think about the next stable release. I would like to start the code freeze after the next release cycle, so two weeks from now. Hopefully, like last time we can keep the freeze period relatively short, so

Release plans

Happy New Year to everyone! As you probably know, 2012 will be the year when we release 1.4. I know I already said this last year, but this time I mean it... The release features are in good shape now, and the plan is to enter code freeze as soon as the DIB engine can be considered done, which s

Re: Release plans

As a user that only uses wine for playing games built for the Windows platform what I would like the most is d3d10, d3d10.1 and d3d11. It seems that these API's are more similar between themselves than what is the difference between d3d9 and d3d10.

Re: Release plans

On Mon, 13 Sep 2010, Edward Savage wrote: [...] > Out of interest why are applications not considered release goals? I'm > sure there is a very good reason I'd just like to know it. Just seems > to me that it would be a good idea to pick a handful of very popular, > but mostly ignored, application

Re: Release plans

On 09/12/2010 06:36 AM, Dan Kegel wrote: > Looks like Alexandre must have fired up his time machine again :-) > > And as long as it's up and running, how about a look forward > at the 1.4 release plans? > > I've discussed this idea with a lot of (non-Wine-Develop

Re: Release plans

On Mon, Sep 13, 2010 at 5:29 AM, Dan Kegel wrote: > James McKenzie wrote: >> Dan Kegel wrote: >>> And as long as it's up and running, how about a look forward >>> at the 1.4 release plans? >> >> Would be nice to know what has priority for this relea

Re: Release plans

On 9/12/10 12:29 PM, Dan Kegel wrote: James McKenzie wrote: Dan Kegel wrote: And as long as it's up and running, how about a look forward at the 1.4 release plans? Would be nice to know what has priority for this release. I would love to see the DIB Engine be the 'deal maker'

Re: Release plans

James McKenzie wrote: > Dan Kegel wrote: >> And as long as it's up and running, how about a look forward >> at the 1.4 release plans? > > Would be nice to know what has priority for this release. > I would love to see the DIB Engine be the 'deal maker'. Ai

Re: Release plans

On 9/12/10 6:36 AM, Dan Kegel wrote: Looks like Alexandre must have fired up his time machine again :-) And I thought I was alone... And as long as it's up and running, how about a look forward at the 1.4 release plans? Would be nice to know what has priority for this release. I would

Re: Release plans

Looks like Alexandre must have fired up his time machine again :-) And as long as it's up and running, how about a look forward at the 1.4 release plans?

Release plans

Folks, There won't be a release this week, since I'll be spending my Friday on an airplane. Release 1.1.44 will be next Friday. If all goes well and I can finish the few remaining bits of 64-bit support, it should be the last release of the 1.1.x series. We'll then enter code freeze and start the

Re: Post-release plans

On 17 July 2010 16:07, Scott Ritchie wrote: > On 07/16/2010 11:22 AM, Alexandre Julliard wrote: >> Folks, >> >> First I want to thank everybody for your great work of the past two >> years. I'm very happy with what we have achieved with 1.2 (even if we >> didn't manage to get the regression number

Re: Post-release plans

On 07/16/2010 11:22 AM, Alexandre Julliard wrote: > Folks, > > First I want to thank everybody for your great work of the past two > years. I'm very happy with what we have achieved with 1.2 (even if we > didn't manage to get the regression numbers down ;-) You should all go > out and have a drink

Post-release plans

Folks, First I want to thank everybody for your great work of the past two years. I'm very happy with what we have achieved with 1.2 (even if we didn't manage to get the regression numbers down ;-) You should all go out and have a drink to celebrate. Code freeze is of course lifted now, so once y

Re: Release plans

Hi, another week and Sunday gone. Lastly Scott had a nice idea about release & "drop in non-deferred patches". I like it too, but no more stat in this area ;) 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2week

Re: Release plans

On 06/20/2010 01:45 PM, wy...@volny.cz wrote: > > Hi, another week and Sunday gone, but this time i tried to look a bit > closely to the numbers... > > 340 regressions <-- release announcement > 356 regressions <-- release announcement + 1week > 339 regressions <-- release announcement + 2weeks(r

Re: Release plans

Hi, another week and Sunday gone, but this time i tried to look a bit closely to the numbers... 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks(rc1) 322 regressions <-- release announcement + 3weeks(rc2) 3

Re: Release plans

Michael Stefaniuc wrote: On 06/13/2010 10:39 AM, wy...@volny.cz wrote: Hi, another week and Sunday gone so time for simple numbers... 340 regressions<-- release announcement 356 regressions<-- release announcement + 1week 339 regressions<-- release announcement + 2weeks(rc1) 322 regressions<--

Re: Release plans

On 06/13/2010 10:39 AM, wy...@volny.cz wrote: Hi, another week and Sunday gone so time for simple numbers... 340 regressions<-- release announcement 356 regressions<-- release announcement + 1week 339 regressions<-- release announcement + 2weeks(rc1) 322 regressions<-- release announcement + 3w

Re: Release plans

Hi, another week and Sunday gone so time for simple numbers... 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks(rc1) 322 regressions <-- release announcement + 3weeks(rc2) 325 regressions <-- release announ

Re: Release plans

> > 340 regressions<-- release announcement > > 356 regressions<-- release announcement + 1week > > 339 regressions<-- release announcement + 2weeks(rc1) > > > 322 regressions<-- release announcement + 3weeks(rc2) > > > 325 regressions<-- release announcement + 4weeks > > As we didn't have a relea

Re: Release plans

On 06/06/2010 11:34 AM, wy...@volny.cz wrote: Hi, another week and Sunday gone so time for simple numbers... 340 regressions<-- release announcement 356 regressions<-- release announcement + 1week 339 regressions<-- release announcement + 2weeks(rc1) 322 regressions<-- release announcement + 3w

Re: Release plans

Hi, another week and Sunday gone so time for simple numbers... 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks(rc1) 322 regressions <-- release announcement + 3weeks(rc2) 325 regressions <-- release announ

Re: Release plans

Hi, another week and Sunday gone so time for simple numbers... 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks(rc1) 322 regressions <-- release announcement + 3weeks(rc2) I think it could be even a

Re: Release plans

On Wed, May 26, 2010 at 8:46 PM, James McKenzie wrote: > joerg-cyril.hoe...@t-systems.com wrote: >> >> Hi, >> >> James Mckenzie wrote: >> >>> >>> Defaulting to $HOME/Desktop and $HOME/Documents is a good first step. >>> >> >> There are more directories: Music, Videos(Movies?), Pictures that IMHO >

Re: Release plans

joerg-cyril.hoe...@t-systems.com wrote: Hi, James Mckenzie wrote: Defaulting to $HOME/Desktop and $HOME/Documents is a good first step. There are more directories: Music, Videos(Movies?), Pictures that IMHO such a patch should add at the same time since that's what MS knows about as we

Re: Release plans

Hi, James Mckenzie wrote: >Defaulting to $HOME/Desktop and $HOME/Documents is a good first step. There are more directories: Music, Videos(Movies?), Pictures that IMHO such a patch should add at the same time since that's what MS knows about as well. Austin English wrote: >I haven't used Tiger i

Re: Release plans

On May 24, 2010, at 9:56 AM, Damjan Jovanovic wrote: > ICNS seems like by far the easiest image file format in existence: > http://en.wikipedia.org/wiki/Apple_Icon_Image It's apparently slightly more complicated than that page suggests, given a simple run-length compression scheme for image data

Re: Release plans

On Mon, May 24, 2010 at 4:26 PM, Steven Edwards wrote: > On Sat, May 22, 2010 at 12:27 PM, Damjan Jovanovic > wrote: >> My latest patch set (http://source.winehq.org/patches/data/61966, >> http://source.winehq.org/patches/data/61967, >> http://source.winehq.org/patches/data/61968, >> http://sour

Re: Release plans

On Sat, May 22, 2010 at 12:27 PM, Damjan Jovanovic wrote: > My latest patch set (http://source.winehq.org/patches/data/61966, > http://source.winehq.org/patches/data/61967, > http://source.winehq.org/patches/data/61968, > http://source.winehq.org/patches/data/61969, > http://source.winehq.org/patc

Re: Release plans

Hi, i know this statistics are not rocket science, but i'm just interested how things are getting better before release 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week 339 regressions <-- release announcement + 2weeks Long list of fixed bugs in 1.2-r

Re: Release plans

On Thu, May 20, 2010 at 10:25 PM, Steven Edwards wrote: > On Thu, May 20, 2010 at 4:17 PM, Steven Edwards wrote: >> I've tried with other PNGs before that we've not generated. Take a >> third party png, edit the Info.plist and change the icon entry to >> instead of pointing at the icns file point

Fw: Re: Release plans

To the list. -Forwarded Message- >From: James Mckenzie >Sent: May 21, 2010 8:20 AM >To: joerg-cyril.hoe...@t-systems.com >Subject: Re: Release plans > >joerg-cyril.hoe...@t-systems.com wrote: >> >>>> And I didn't write trivial Mac patches e

Re: Release plans

Austin English wrote: > >On Fri, May 21, 2010 at 3:47 AM, wrote: And I didn't write trivial Mac patches either, e.g. to have wineprefixcreate symlink c:\users\xyz\ Desktop + Videos + Documents + Music to /Users/xyz/Desktop/ etc.  This happens on Linux, not on MacOS. That's an

Re: Release plans

On Fri, May 21, 2010 at 3:47 AM, wrote: >>> And I didn't write trivial Mac patches either, e.g. to have >>> wineprefixcreate symlink c:\users\xyz\ Desktop + Videos + Documents + >>> Music to /Users/xyz/Desktop/ etc.  This happens on Linux, not on MacOS. >>> That's another (example of a) missing e

Fw: Re: Release plans

To the list -Forwarded Message- >From: James Mckenzie >Sent: May 20, 2010 12:49 PM >To: Damjan Jovanovic >Subject: Re: Release plans > >> >>On Fri, May 14, 2010 at 12:31 PM, wrote: >>> Hi, >> >>Hi >> >>>>The 64-b

Release plans

Hi, Damjan Jovanovic wrote: >winemenubuilder generates .png only for 24 and 32 bits-per-pixel >icons, all other resolutions get converted to .xpm. I am planning to >change it to make .png's for everything, since thumbnailing .lnk files >requires .png as output Good to know. This answers my questio

Re: Release plans

On Thu, May 20, 2010 at 4:17 PM, Steven Edwards wrote: > I've tried with other PNGs before that we've not generated. Take a > third party png, edit the Info.plist and change the icon entry to > instead of pointing at the icns file point at the new Png image. Of > course I've tried this on Leopard,

Re: Release plans

On Thu, May 20, 2010 at 4:13 PM, Damjan Jovanovic wrote: > Everything in the .png generation looks bog standard, but maybe MacOS > doesn't like our PNG comment. Try remove that ppng_set_text call in > winemenubuilder's SaveIconResAsPNG and see if it helps? I've tried with other PNGs before that w

Re: Release plans

On Thu, May 20, 2010 at 9:51 PM, Steven Edwards wrote: > > > On Thu, May 20, 2010 at 3:44 PM, Steven Edwards > wrote: >> >> I have a hacked version in the Bordeaux tree that uses sips to create >> icns icons and working Application bundles. If they have time, Austin >> or Tom can send it along fo

Re: Release plans

On Thu, May 20, 2010 at 3:44 PM, Steven Edwards wrote: > I have a hacked version in the Bordeaux tree that uses sips to create > icns icons and working Application bundles. If they have time, Austin > or Tom can send it along for your review if your interested. The > 'right' solution would be to f

Re: Release plans

On Thu, May 20, 2010 at 3:08 PM, Damjan Jovanovic wrote: > winemenubuilder generates .png only for 24 and 32 bits-per-pixel > icons, all other resolutions get converted to .xpm. I am planning to > change it to make .png's for everything, since thumbnailing .lnk files > requires .png as output, and

Re: Release plans

On Fri, May 14, 2010 at 12:31 PM, wrote: > Hi, Hi >>The 64-bit support is now more or less complete > I hope I can finish my MCI parser patches in time. Without them, > every 64bit app using MCI string commands is likely to crash (OTOH > MCI commands work (those using the MCI_*_PARAMS structure

Re: Release plans

> > >Hi, > >some time passed and because statistics are somewhat popular here, i >did one ;) > >340 regressions <-- release announcement >356 regressions <-- release announcement + 1week > Not a good statistic, but maybe we caused a few folks to decide to submit overdue regressions now that Win

Re: Release plans

Hi, some time passed and because statistics are somewhat popular here, i did one ;) 340 regressions <-- release announcement 356 regressions <-- release announcement + 1week So we are not converging... Will there be at least an effort to fix all the regression or should i go and crawl throug

Re: Release plans

Edward Savage wrote: > On Sat, May 15, 2010 at 1:11 AM, Jeremy White wrote: >> I can't find anything on that release, but we're certainly happy to >> put together another one for Wine 1.2. I've CC'd Jon Parshall, as he's >> the guy that'll get to do it. >> > > Could you link us to a copy of the

Re: Release plans

On Sat, May 15, 2010 at 1:11 AM, Jeremy White wrote: > > I can't find anything on that release, but we're certainly happy to > put together another one for Wine 1.2.  I've CC'd Jon Parshall, as he's > the guy that'll get to do it. > Could you link us to a copy of the 1.0 one? Some one profession

Re: Release plans

Hey Brian, > > Jeremy - do you have a copy of the real press release we did for 1.0? I > dug around looking for it and couldn't find it. Looks like we never > properly posted it on WineHQ. It did get picked up by quite a few news > sites, but Google isn't finding it. > > Scott / Edward - whe

Release plans

Hi, >The 64-bit support is now more or less complete I hope I can finish my MCI parser patches in time. Without them, every 64bit app using MCI string commands is likely to crash (OTOH MCI commands work (those using the MCI_*_PARAMS structures)). What can Mac users expect from this release? Yes

Re: Release plans

On Wed, 12 May 2010, Alexandre Julliard wrote: > Scott Ritchie writes: > > > On 05/09/2010 05:00 PM, Alexandre Julliard wrote: > >> We definitely need a release changelog, yes. > > > > It seems to me what we really want is more than a changelog but a proper > > release announcement. I want a jo

Re: Release plans

> >On 05/09/2010 05:00 PM, Alexandre Julliard wrote: >> Edward Savage writes: >> >>> On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard >>> wrote: Unless some major problems come up, 1.1.44 will be the last of the 1.1.x series. The next release will be 1.2-rc1, which will mark th

Re: Release plans

Scott Ritchie writes: > On 05/09/2010 05:00 PM, Alexandre Julliard wrote: >> We definitely need a release changelog, yes. > > It seems to me what we really want is more than a changelog but a proper > release announcement. I want a journalist who has hardly heard of Wine > to read the page and u

Re: Release plans

On Wed, May 12, 2010 at 11:27 AM, Brian Vincent wrote: > Also, what would be really good would be to provide some contact information > for people that can be used by the press to ask some simple questions about > the release.  It'd be good to have a European contact and a US one. >  However, be p

Re: Release plans

On Wed, May 12, 2010 at 9:29 AM, Edward Savage wrote: > On Thu, May 13, 2010 at 1:08 AM, Scott Ritchie > wrote: > > > > It seems to me what we really want is more than a changelog but a proper > > release announcement. I want a journalist who has hardly heard of Wine > > to read the page and un

Re: Release plans

On Thu, May 13, 2010 at 1:08 AM, Scott Ritchie wrote: > > It seems to me what we really want is more than a changelog but a proper > release announcement.  I want a journalist who has hardly heard of Wine > to read the page and understand what we've done and why it's great. > > I've created a roug

Re: Release plans

On 05/09/2010 05:00 PM, Alexandre Julliard wrote: > Edward Savage writes: > >> On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard >> wrote: >>> >>> Unless some major problems come up, 1.1.44 will be the last of the 1.1.x >>> series. The next release will be 1.2-rc1, which will mark the beginnin

Re: Release plans

--- On Mon, 10/5/10, Alexandre Julliard wrote: > > The last time I checked it was possible to re-use an > old wineprefix > > (created by 32-bit wine under x86_64 platform) with > 64-bit wine - is > > it still the case? My .wine is a bit big and I'd hate > to have to > > re-create it... :-(. I me

Re: Release plans

Alexandre Julliard wrote: Ben Klein writes: I'm more interested to know in the status of WoW64 in Wine. Can 64bit and 32bit Wine be installed sensibly and concurrently? Yes, everything should work as expected now. Please test it. The last time I checked it was possible to re-use an old win

Re: Release plans

Hin-Tak Leung writes: > Alexandre Julliard wrote: >> Ben Klein writes: >> >>> I'm more interested to know in the status of WoW64 in Wine. Can 64bit >>> and 32bit Wine be installed sensibly and concurrently? >> >> Yes, everything should work as expected now. Please test it. > > The last time I ch

Re: Release plans

Edward Savage writes: > On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard > wrote: >> >> Unless some major problems come up, 1.1.44 will be the last of the 1.1.x >> series. The next release will be 1.2-rc1, which will mark the beginning >> of the code freeze. This should result in a 1.2 final

Re: Release plans

On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard wrote: > > Unless some major problems come up, 1.1.44 will be the last of the 1.1.x > series. The next release will be 1.2-rc1, which will mark the beginning > of the code freeze. This should result in a 1.2 final sometime in June. > Would it be

Re: Release plans

Tom Wickline writes: > I thought the code freeze, RC cycle would be more like three months not > three releases, e.g six weeks. > But I'm 100% sure AJ knows best. :) Nobody said it can't be three months. It will last as long as good fixes keep pouring in. In practice after 1-2 months we usually

Re: Release plans

Ben Klein writes: > I'm more interested to know in the status of WoW64 in Wine. Can 64bit > and 32bit Wine be installed sensibly and concurrently? Yes, everything should work as expected now. Please test it. -- Alexandre Julliard julli...@winehq.org

Re: Release plans

2010/5/9 Sir Gallantmon (ニール・ゴンパ) : > On Sat, May 8, 2010 at 1:42 PM, Alexandre Julliard > wrote: >> >> Folks, >> >> The 64-bit support is now more or less complete, and we have most of the >> fancy new icons, so it's time to think about the next stable release. > > What do you mean by the 64-bit

Re: Release plans

Vincent Povirk wrote: Actually, when I read through the report, it broke in 1.0-rc4 but worked in 0.9.52. That is one old bug and aggravating too. You're right, so it didn't work in 1.0. That's.. that might actually be worse. Vincent: This should be on the 1.2 todo list. This real

Re: Release plans

On Sat, May 8, 2010 at 8:43 PM, Erich Hoover wrote: > On Sat, May 8, 2010 at 7:16 PM, Vincent Povirk > wrote: >> >> While we're linking to bug lists, this one seems most interesting to me: >> http://bit.ly/bfOHK5 >> >> That's the list of major regressions introduced since 1.0-rc1. >> ... > > What

Re: Release plans

On Sat, May 8, 2010 at 7:16 PM, Vincent Povirk wrote: > While we're linking to bug lists, this one seems most interesting to me: > http://bit.ly/bfOHK5 > > That's the list of major regressions introduced since 1.0-rc1. > ... > What criteria did you use to build that list? There's a bunch of rece

Re: Release plans

> Actually, when I read through the report, it broke in 1.0-rc4 but worked in > 0.9.52.  That is one old bug and aggravating too. You're right, so it didn't work in 1.0. That's.. that might actually be worse.

Re: Release plans

Vincent Povirk wrote: While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5 That's the list of major regressions introduced since 1.0-rc1. Bug 13891 in particular will make us look bad if it's not fixed before 1.2. A lot of apps (as I understand it, any a

Re: Release plans

Vincent Povirk wrote: While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5 That's the list of major regressions introduced since 1.0-rc1. Bug 13891 in particular will make us look bad if it's not fixed before 1.2. A lot of apps (as I understand it, any a

Re: Release plans

While we're linking to bug lists, this one seems most interesting to me: http://bit.ly/bfOHK5 That's the list of major regressions introduced since 1.0-rc1. Bug 13891 in particular will make us look bad if it's not fixed before 1.2. A lot of apps (as I understand it, any app that does it properly

Re: Release plans

On Sun, May 9, 2010 at 7:02 AM, Dan Kegel wrote: > Tom Wickline wrote: > >> > http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&target_milestone=1.2.0 > > > > Three releases to fix 88 nasty bugs? > > The sad fact is that

re: Release plans

Tom Wickline wrote: >> http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&target_milestone=1.2.0 > > Three releases to fix 88 nasty bugs? The sad fact is that it would take a lot more than that to fix them all, and it proba

Re: Release plans

On Sun, May 9, 2010 at 4:34 AM, Austin English wrote: > > It's the first link on the tasklist in bugzilla: > > http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&target_milestone=1.2.0&order=bugs.bug_severity > > -- > -Aust

Re: Release plans

On Sat, May 8, 2010 at 3:31 PM, James McKenzie wrote: > Alexandre Julliard wrote: >> >> Folks, >> >> The 64-bit support is now more or less complete, and we have most of the >> fancy new icons, so it's time to think about the next stable release. >> >> Unless some major problems come up, 1.1.44 wi

Re: Release plans

Alexandre Julliard wrote: Folks, The 64-bit support is now more or less complete, and we have most of the fancy new icons, so it's time to think about the next stable release. Unless some major problems come up, 1.1.44 will be the last of the 1.1.x series. The next release will be 1.2-rc1, whic

Re: Release plans

On Sat, May 8, 2010 at 1:42 PM, Alexandre Julliard wrote: > Folks, > > The 64-bit support is now more or less complete, and we have most of the > fancy new icons, so it's time to think about the next stable release. > > Unless some major problems come up, 1.1.44 will be the last of the 1.1.x > ser

Release plans

Folks, The 64-bit support is now more or less complete, and we have most of the fancy new icons, so it's time to think about the next stable release. Unless some major problems come up, 1.1.44 will be the last of the 1.1.x series. The next release will be 1.2-rc1, which will mark the beginning of

Re: Release plans

On 10/1/05, Francois Gouget <[EMAIL PROTECTED]> wrote: > On Sat, 1 Oct 2005, Brian Vincent wrote: > > > On 10/1/05, Molle Bestefich <[EMAIL PROTECTED]> wrote: > >> Question is, how do I convey updates to the documentation to you guys? > > > > Tom described it here: > > http://www.winehq.com/?issue=

Re: Release plans

On Mon, 03 Oct 2005 19:15:20 +0200, Holly Bostick wrote: > As far as I know, Gentoo (along with many other distros) cleaned up their > act w.r.t wine several months ago (when Mike Hearn, I believe, got the > various maintainers to *pay attention* to Wine development, rather than > just assuming tha

Re: Release plans

Holly Bostick wrote: If you don't want to go by, the bug has been downgraded from 'normal' to 'trivial' (which it rather is), and a suggestion has been made that, rather than writing a patch against the wine sources (and having to maintain it), an einfo should be added to the ebuild telling use

Re: Release plans

Brian Vincent schreef: > On 10/3/05, Jonathan Ernst <[EMAIL PROTECTED]> wrote: > >> Gentoo builds everything in some sandbox in /var/tmp and then >> copies everything in the right places. Wine seems to think files >> will stay in that directory altough they won't. However I'm quite >> sure everyth

Re: Release plans

Le lundi 03 octobre 2005 à 10:13 -0600, Brian Vincent a écrit : > On 10/3/05, Jonathan Ernst <[EMAIL PROTECTED]> wrote: > > Gentoo builds everything in some sandbox in /var/tmp and then copies > > everything in the right places. Wine seems to think files will stay in > > that directory altough they

Re: Release plans

On 10/3/05, Jonathan Ernst <[EMAIL PROTECTED]> wrote: > Gentoo builds everything in some sandbox in /var/tmp and then copies > everything in the right places. Wine seems to think files will stay in > that directory altough they won't. However I'm quite sure everything > will work as expected. Ther

Re: Release plans

On 10/3/05, Molle Bestefich <[EMAIL PROTECTED]> wrote: > > > What sort of errors do you get? > > The installer can't create it's installation directory. > Creating the directory manually does not help. > For now you have to use native comctl32 to install some apps. -- James Hawkins

Re: Release plans

Le lundi 03 octobre 2005 à 12:19 +0200, Holly Bostick a écrit : [...] > P.S. --Jonathan, been meaning to ask you; is it possible for you to > upload your public GPG to a server somewhere? It would be nice to get > rid of the yellow "Unverified Signature" warning I get from Enigmail > every time I r

Re: Release plans

Jonathan Ernst schreef: > Le dimanche 02 octobre 2005 à 15:45 -0600, Brian Vincent a écrit : > >>> I don't even know how to debug this-- or even if it needs >>> debugging-- as I don't know how to tell the difference between >>> how Wine would act if the libraries cannot be found because of a >>

Re: Release plans

I wrote: > I wrote: > > Maybe there are much better solutions out there, which could also > > spare you some precious time having to do those Bugzilla reports you > > are currently making... > > > > See for instance Trac, which has built-in reports, and where the user > > can in a very simple way c

Re: Release plans

Le dimanche 02 octobre 2005 à 15:45 -0600, Brian Vincent a écrit : > > I don't even know how to debug this-- or even if it needs debugging-- as > > I don't know how to tell the difference between how Wine would act if > > the libraries cannot be found because of a lack of this update, and how > > W

Re: Release plans

James Liggett wrote: > Molle Bestefich wrote: > > There's a newer (4.8) IDA Pro demo, but alas, it cannot be installed > > under WINE CVS HEAD :-/. > > That's odd...I got IDA 4.8 demo to install and work without any problems > at all. Perhaps something broke recently? Must have. Recently? Not so

Re: Release plans

On Fri, 2005-09-30 at 15:11 -0600, Tony Lambregts wrote: > I have a question though what should I call this release in bugzilla? > > 20050930 > 20050930 pre beta 0.9.0 > 0.9.0 pre beta (20050930) > > other suggestions Keep it in synch with the real release. 20050930 should do just fine. --

Re: Release plans

On Sat, 2005-10-01 at 20:12 +0200, Francois Gouget wrote: > Btw, why not put the Wine documentation in the same CVS as the Wine > sources, Website, the AppDB, etc. It seems like this would simplify > explaining how to get it a lot (and it would automatically work with > cvsup too). It's just si

Re: Release plans

On Sunday 02 October 2005 5:45 pm, Brian Vincent wrote: > Maybe we need to collect things like this into a "Release Notes" page > on the wiki? In this case it would look something like, "GENTOO > USERS: After placing the bullets in the chamber, pointing the gun at > your foot, and typing emerge yo

Re: Release plans

On Sun, 2005-10-02 at 20:18 +, Molle Bestefich wrote: > Brian Vincent wrote: > > Anyway, the filename here has "demo" in it, so I'm not sure if this is > > the full IDA Pro everyone has used in the past. > > http://www.download.com/IDA-The-Interactive-Disassembler/3000-2218_4-10361515.html?tag=

Re: Release plans

> I don't even know how to debug this-- or even if it needs debugging-- as > I don't know how to tell the difference between how Wine would act if > the libraries cannot be found because of a lack of this update, and how > Wine acts when the environment has been correctly updated. My $.02 is if yo

Re: Release plans

Marcus Meissner wrote: > > Where we're at now: > > * None of the IDA versions actually both install and work under Wine. > > You can buy it. It then comes with a Linux console version. > > Its however pretty high priced. Hehe. Guess that's not an option, then. > The Windows GUI version of IDA wo

Re: Release plans

> Where we're at now: > * None of the IDA versions actually both install and work under Wine. You can buy it. It then comes with a Linux console version. Its however pretty high priced. The Windows GUI version of IDA works fine, the Win32 console version too. Don't remember the install anymore ;

Re: Release plans

Alexandre Julliard schreef: > Folks, > > I just released 20050930, this should be considered the pre-0.9 > release, so please give it some good testing. In particular, please > test the things that new users will encounter first, like the > automatic .wine creation and winecfg. > > Even if you

Re: Release plans

Brian Vincent wrote: > Anyway, the filename here has "demo" in it, so I'm not sure if this is > the full IDA Pro everyone has used in the past. > http://www.download.com/IDA-The-Interactive-Disassembler/3000-2218_4-10361515.html?tag=lst-0-1 No-go, that version expires in 1998. There's a newer (4.

Re: Release plans

On 10/1/05, Molle Bestefich <[EMAIL PROTECTED]> wrote: > > Anyway, I'm trying hard to come up with a web page that > > makes it easy for even non-wine-developers to help > > triage bug reports. [ http://kegel.com/wine/qa ] > > You asked for feedback from non-wine-developers, so here's my 2 cents.

  1   2   >