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 the code freeze. This should result in a 1.2 final sometime in June. As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute. I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late. -- Alexandre Julliard julliard(a)winehq.org
On Sat, May 8, 2010 at 1:42 PM, Alexandre Julliard <julliard(a)winehq.org>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, which will mark the beginning of the code freeze. This should result in a 1.2 final sometime in June.
As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute.
I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late.
-- Alexandre Julliard julliard(a)winehq.org
What do you mean by the 64-bit support being "more or less complete"?
2010/5/9 Sir Gallantmon (ニール・ゴンパ) <ngompa13(a)gmail.com>:
On Sat, May 8, 2010 at 1:42 PM, Alexandre Julliard <julliard(a)winehq.org> 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 support being "more or less complete"?
I'm more interested to know in the status of WoW64 in Wine. Can 64bit and 32bit Wine be installed sensibly and concurrently?
Alexandre Julliard wrote:
Ben Klein <shacklein(a)gmail.com> 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 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... :-(. Hin-Tak
Hin-Tak Leung <hintak_leung(a)yahoo.co.uk> writes:
Alexandre Julliard wrote:
Ben Klein <shacklein(a)gmail.com> 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 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... :-(.
You can use a 32-bit prefix with 64-bit Wine, but of course only in 32-bit mode, you won't be able to run 64-bit apps with it. -- Alexandre Julliard julliard(a)winehq.org
--- On Mon, 10/5/10, Alexandre Julliard <julliard(a)winehq.org> 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 meant to write "wasn't possible" . Sorry about that.
You can use a 32-bit prefix with 64-bit Wine, but of course only in 32-bit mode, you won't be able to run 64-bit apps with it.
It is all a bit confusing - see (https://bugzilla.redhat.com/show_bug.cgi?id=533806) I think the last time I tried both, I did encounter the problem with '/home/myuzer/.wine' is a 32-bit prefix, it cannot be used with 64-bit Wine. I think a wiki/FAQ could be useful - there is an FAQ somewhere which says one should use a different prefix for 32-bit wine vs 64-bit wine on platforms which can do both. My concern is that I have a fairly big ${HOME}/.wine and I'd prefer to continue to use it, or at least it doesn't get messed up if I switch to 64-bit wine.
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, which will mark the beginning of the code freeze. This should result in a 1.2 final sometime in June.
As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute.
I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late.
AJ: I would be nice to include the URL as well for the 1.2 buglist. James McKenzie
On Sat, May 8, 2010 at 3:31 PM, James McKenzie <jjmckenzie51(a)earthlink.net> 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 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.
As usual the code freeze will become more and more drastic as we get closer to release, so if you have major changes to make, now is pretty much the last minute.
I'd encourage everyone to look through the list of nominated 1.2 bugs, and also to check the regression reports for anything that might be in your area. We should strive to have as few regressions from 1.0 as possible, so regressions fixes will have priority during code freeze. And of course changes that don't impact the code, like translations or test fixes, can go in until quite late.
AJ:
I would be nice to include the URL as well for the 1.2 buglist.
It's the first link on the tasklist in bugzilla: http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug... -- -Austin
On Sun, May 9, 2010 at 4:34 AM, Austin English <austinenglish(a)gmail.com>wrote:
It's the first link on the tasklist in bugzilla:
http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug...
-- -Austin
Three releases to fix 88 nasty bugs? -- Tom
On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard <julliard(a)winehq.org> 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 worthwhile to put together some sort of release announcement detailing changes and improvements in Wine between 1 and 1.2? Some thing similar to what other projects release that tech sites can pickup and talk about. Maybe even a more formal press release style document. If not I feel it might be good to have a page, nicely formatted with graphics, that listed some applications that run as-native that people not using Wine can try so that they become familiar with the application. We could easily compile a list of 10-15 popular platinum applications that those who discredit Wine would be surprised run well. A small blurb and some nice screen shots of each application with links to their respective Appdb and Wikipedia entries would be good. I am volunteering to organise some thing like this if wanted but it'd have to be some thing people were comfortable with and like the idea of.
Edward Savage <epssyis(a)gmail.com> writes:
On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard <julliard(a)winehq.org> 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 worthwhile to put together some sort of release announcement detailing changes and improvements in Wine between 1 and 1.2? Some thing similar to what other projects release that tech sites can pickup and talk about. Maybe even a more formal press release style document.
We definitely need a release changelog, yes. -- Alexandre Julliard julliard(a)winehq.org
On 05/09/2010 05:00 PM, Alexandre Julliard wrote:
Edward Savage <epssyis(a)gmail.com> writes:
On Sun, May 9, 2010 at 4:42 AM, Alexandre Julliard <julliard(a)winehq.org> 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 worthwhile to put together some sort of release announcement detailing changes and improvements in Wine between 1 and 1.2? Some thing similar to what other projects release that tech sites can pickup and talk about. Maybe even a more formal press release style document.
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 understand what we've done and why it's great. I've created a rough skeleton of things to have here: http://wiki.winehq.org/Wine1.2Announcement I'm very busy at the Ubuntu Developer Summit at the moment but I'll put some good work into it soon. Thanks, Scott Ritchie
On Thu, May 13, 2010 at 1:08 AM, Scott Ritchie <scott(a)open-vote.org> 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 rough skeleton of things to have here: http://wiki.winehq.org/Wine1.2Announcement
I'm very busy at the Ubuntu Developer Summit at the moment but I'll put some good work into it soon.
I was strongly alluding to this. I am not a journalist though I did get forced to take a course in it for a university elective so I know the basics and I am a big fan of writing. I have been considering the best way to frame Wine to get the most attention and new users. I will update that wiki page with my ideas and start fleshing out some blocks of content. I have almost no written work for people to see beyond some stories I wrote for an as-yet unreleased copy of WWN. http://home.bluesata.com/WineWWN/WineHQ/wwn/362 Still I think I'd be up to the task to write some thing worthwhile.
On Wed, May 12, 2010 at 9:29 AM, Edward Savage <epssyis(a)gmail.com> wrote:
On Thu, May 13, 2010 at 1:08 AM, Scott Ritchie <scott(a)open-vote.org> 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.
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 - when 1.0 came out, Jeremy had the PR firm that writes copy for Codeweavers put together a press release for Wine. It was pretty good and fairly polished. I'm not sure if having them do it again would be an option. Also, I think Wine 1.0 was coordinated with a release of Crossover 7.0. 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 prepared to actually get called and be available by email to answer questions. News sites like to turn articles around in a matter of hours, so it needs a tiny bit of attention. PS - Hung out with Mike McCormack on Monday. It was good to see him again. -Brian
On Wed, May 12, 2010 at 11:27 AM, Brian Vincent <brian.vincent(a)gmail.com> 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 prepared to actually get called and be available by email to answer questions. News sites like to turn articles around in a matter of hours, so it needs a tiny bit of attention.
There's press(a)winehq.org, which gets sent to a few people. See http://bugs.winehq.org/show_bug.cgi?id=20603 That doesn't have phone numbers, though. However, between all of us, I'm sure someone will see the email fairly quickly. -- -Austin
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 - when 1.0 came out, Jeremy had the PR firm that writes copy for Codeweavers put together a press release for Wine. It was pretty good and fairly polished. I'm not sure if having them do it again would be an option. Also, I think Wine 1.0 was coordinated with a release of Crossover 7.0.
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. Cheers, Jeremy
On Sat, May 15, 2010 at 1:11 AM, Jeremy White <jwhite(a)codeweavers.com> 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 professional doing the release would be really cool. If that is sorted I really want to do a short showcase of applications that do run well now under Wine (and maybe Crossover? ie Chrome) with a blurb and screen shot for them. A static page that can be linked to for people who want to quickly check out the progress instead of trudging through the appdb.
Edward Savage wrote:
On Sat, May 15, 2010 at 1:11 AM, Jeremy White <jwhite(a)codeweavers.com> 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?
Um, no; that's what I meant when I said I couldn't find anything on it <grin>. In fact, our PR firm is questioning our sanity - are we really sure we did a release? I'm not sure a release is all that advantageous; it goes over the wire to overwhelmed newsprint reporters who usually ignore it. An announcement is quite likely to be picked up on places like Slashdot and Digg, and that then tends to spur internet buzz far and wide. So...an announcement may be all we really need. Cheers, Jeremy
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 through them and nominate them as milestone 1.2? Don't take this bad, just a question ;) I hope that fixing them all is the right way, which will save me time with nominating.
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-rc1 is also quite impressive. Thank you all!
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 bit better, if all the bugs we retested since friday changed their ;) I guess, that around rc11 it will look pretty good.
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 announcement + 4weeks Good trend from pasted weeks took a nap.
On 06/06/2010 11:34 AM, wylda(a)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 + 3weeks(rc2) 325 regressions<-- release announcement + 4weeks
As we didn't have a release last Friday shouldn't you subtract the "RESOLVED and FIXED" ones? Or do you 'ignore' these until possible fixes are actually committed? -- Cheers, Paul.
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 release last Friday shouldn't you subtract the "RESOLVED and FIXED" ones? Or do you 'ignore' these until possible fixes are actually committed?
That's what i always did, i.e. there is 340 unclosed regressions, but 15 are RESOLVED, so that's where 325 comes from. BTW: I'm in process of recovery of my winetest maschine AKA WyldBOT (MOBO came back from Asus repair center).
Scott Ritchie <scott(a)open-vote.org> 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 understand what we've done and why it's great.
Sure, that's the press release, we should have one too, but it's a different thing. A changelog would be a detailed description of changes that matter from a user point of view. It would list for instance new builtin programs, new configuration options, new behaviors, new system dependencies, backwards compatibility concerns, etc. You can't put that sort of things in the press release. -- Alexandre Julliard julliard(a)winehq.org
On Wed, 12 May 2010, Alexandre Julliard wrote:
Scott Ritchie <scott(a)open-vote.org> 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 understand what we've done and why it's great.
Sure, that's the press release, we should have one too, but it's a different thing. A changelog would be a detailed description of changes that matter from a user point of view. It would list for instance new builtin programs, new configuration options, new behaviors, new system dependencies, backwards compatibility concerns, etc.
Isn't that more a release notes document? So we'd have: * Press Release Announcing the new Wine to the world at large. Must be readable by people who have never heard of Wine before. * Release notes A user friendly and high-level description what's new and what's changed. * Changelog A detailed description of what's changed from a developper perspective, that is the usual list of commit messages. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ If it stinks, it's chemistry. If it moves, it's biology. If it does not work, It's computer science.
participants (14)
-
Alexandre Julliard -
Austin English -
Ben Klein -
Brian Vincent -
Edward Savage -
Francois Gouget -
Hin-Tak Leung -
James McKenzie -
Jeremy White -
Paul Vriens -
Scott Ritchie -
Sir Gallantmon (ニール・ゴンパ) -
Tom Wickline -
wylda＠volny.cz