Building the 1.6 Release Notes as things are written.

2012-03-08 Thread Scott Ritchie
So, congrats everyone, 1.4 is out and I'm very happy about it :) I wanted to thank Alexandre for his release announcement, it was very through and informative. It also looked like a lot of work. This made me wonder if we could instead build up the announcement gradually with some sort of proces

A request about the release notes

2011-06-01 Thread Scott Ritchie
. In my case I only noticed when a bug report came in and I manually looked at the package build log. This sort of thing would be much less likely to happen if such a build dependency change were noted in the release notes, such as a "OSS 3 no longer supported" bullet point. Thanks, Scott Ritchie

Re: Wine-1.0 release notes

2008-06-13 Thread Steven Edwards
On Thu, Jun 12, 2008 at 3:20 AM, Reece Dunn <[EMAIL PROTECTED]> wrote: > Does anyone know what the state of installing/running Office 2003 is, > because I seem to recall there being a regression in this area. That > is something that I would consider a blocker. It installs fine, however almost not

Re: Wine-1.0 release notes

2008-06-13 Thread Reece Dunn
. Another regression was the result of cleaning up deprecated alsa calls that broke older alsa drivers on various distributions (which I happened to spot - I thought it might have been the pulseaudio adapter, but my machine is currently using a real alsa driver). Regressions happen. If they are in ap

Re: Wine-1.0 release notes

2008-06-12 Thread Steven Edwards
On Thu, Jun 12, 2008 at 9:32 AM, Austin English <[EMAIL PROTECTED]> wrote: > The bugs may be deferred, but if the bugs aren't reported, no one > knows to fix them, albeit not likely until after 1.0. If I recall correctly the criteria for target applications was that they be freely accessible such

Re: Wine-1.0 release notes

2008-06-12 Thread Tom Wickline
On Thu, Jun 12, 2008 at 9:32 AM, Austin English <[EMAIL PROTECTED]> wrote: > > The bugs may be deferred, but if the bugs aren't reported, no one > knows to fix them, albeit not likely until after 1.0. > > Not reporting bugs is the software equivalent of people who don't vote > and expect politician

Re: Wine-1.0 release notes

2008-06-12 Thread Austin English
On Thu, Jun 12, 2008 at 7:51 AM, Tom Wickline <[EMAIL PROTECTED]> wrote: > On Thu, Jun 12, 2008 at 8:01 AM, Zachary Goldberg <[EMAIL PROTECTED]> wrote: >> On Thu, Jun 12, 2008 at 6:04 AM, Tom Wickline <[EMAIL PROTECTED]> wrote: >>> On Wed, Jun 11, 2008 at 9:52 PM, Vitaliy Margolen >>> <[EMAIL PROTE

Re: Wine-1.0 release notes

2008-06-12 Thread Tom Wickline
On Thu, Jun 12, 2008 at 8:01 AM, Zachary Goldberg <[EMAIL PROTECTED]> wrote: > On Thu, Jun 12, 2008 at 6:04 AM, Tom Wickline <[EMAIL PROTECTED]> wrote: >> On Wed, Jun 11, 2008 at 9:52 PM, Vitaliy Margolen >> <[EMAIL PROTECTED]> wrote: >>> Scott Ritchie wrote: In any case, we should note why we

Re: Wine-1.0 release notes

2008-06-12 Thread Zachary Goldberg
On Thu, Jun 12, 2008 at 6:04 AM, Tom Wickline <[EMAIL PROTECTED]> wrote: > On Wed, Jun 11, 2008 at 9:52 PM, Vitaliy Margolen > <[EMAIL PROTECTED]> wrote: >> Scott Ritchie wrote: >>> In any case, we should note why we're making a release in the first >>> place, and make it very clear that we believe

Re: Wine-1.0 release notes

2008-06-12 Thread Austin English
On Thu, Jun 12, 2008 at 5:04 AM, Tom Wickline <[EMAIL PROTECTED]> wrote: > On Wed, Jun 11, 2008 at 9:52 PM, Vitaliy Margolen > <[EMAIL PROTECTED]> wrote: >> Scott Ritchie wrote: >>> In any case, we should note why we're making a release in the first >>> place, and make it very clear that we believe

Re: Wine-1.0 release notes

2008-06-12 Thread Tom Wickline
On Wed, Jun 11, 2008 at 9:52 PM, Vitaliy Margolen <[EMAIL PROTECTED]> wrote: > Scott Ritchie wrote: >> In any case, we should note why we're making a release in the first >> place, and make it very clear that we believe Wine 1.0 to be the best >> version of Wine yet in all cases (ie, no regressions

Re: Wine-1.0 release notes

2008-06-11 Thread Vitaliy Margolen
Vitaliy Margolen wrote: > Since all of the 1.0 blocker bugs being pushed back, wine-1.0 release notes > should list all of those as major known problems. Otherwise people will get > a bad impression that wine-1.0 means more then less working release. > > Also release notes shou

Re: Wine-1.0 release notes

2008-06-11 Thread Vitaliy Margolen
Scott Ritchie wrote: > In any case, we should note why we're making a release in the first > place, and make it very clear that we believe Wine 1.0 to be the best > version of Wine yet in all cases (ie, no regressions). I'd disagree on "the best" part. Looking at bugzilla and forum people thing t

Re: Wine-1.0 release notes

2008-06-11 Thread Susan Cragin
mean, how proud do we need to be about not running everything? Susan -Original Message- >From: Reece Dunn <[EMAIL PROTECTED]> >Sent: Jun 11, 2008 8:02 PM >To: Vitaliy Margolen <[EMAIL PROTECTED]> >Cc: Wine Develop >Subject: Re: Wine-1.0 release notes > >200

Re: Wine-1.0 release notes

2008-06-11 Thread Vitaliy Margolen
Reece Dunn wrote: > 2008/6/11 Vitaliy Margolen <[EMAIL PROTECTED]>: >> In short - that after everyone's hard work and 15 years of development >> wine-1.0 is just a release tag nothing more. > > I think that this is overly harsh. It's like saying that you should > not celebrate a birthday, as that

Re: Wine-1.0 release notes

2008-06-11 Thread Reece Dunn
work. But think of all the applications that *do* work; given what Wine is working against, this is an amasing achievement. Wine can and does run Office, Photoshop, ITunes, Oblivion, Peggle and a myriad other applications (some better than others). So yes, highlight the known issues in the release

Re: Wine-1.0 release notes

2008-06-11 Thread Scott Ritchie
Vitaliy Margolen wrote: > Since all of the 1.0 blocker bugs being pushed back, wine-1.0 release notes > should list all of those as major known problems. Otherwise people will get > a bad impression that wine-1.0 means more then less working release. > > Also release notes shou

Re: Wine-1.0 release notes

2008-06-11 Thread Steven Edwards
On Wed, Jun 11, 2008 at 6:56 PM, Vitaliy Margolen <[EMAIL PROTECTED]> wrote: > In short - that after everyone's hard work and 15 years of development > wine-1.0 is just a release tag nothing more. I think this deserves more discussion but I am not quite ready. I'll post a reply on Monday as an RFC

Wine-1.0 release notes

2008-06-11 Thread Vitaliy Margolen
Since all of the 1.0 blocker bugs being pushed back, wine-1.0 release notes should list all of those as major known problems. Otherwise people will get a bad impression that wine-1.0 means more then less working release. Also release notes should mention that wine-1.0 is not suitable for most

Re: Release notes

2007-03-30 Thread Stefan Dösinger
Am Freitag 30 März 2007 22:26 schrieb John Voltz: > I have a question about the Wine release notes. Do the Wine developers > work from bugzilla or do they usually just work on a specific > application feature? Would it require too much extra effort on the > release notes to associat

Release notes

2007-03-30 Thread John Voltz
I have a question about the Wine release notes. Do the Wine developers work from bugzilla or do they usually just work on a specific application feature? Would it require too much extra effort on the release notes to associate a specific change with a bugzilla bug-fix or specific application

Re: Release notes

2005-05-25 Thread Mike Hearn
On Tue, 24 May 2005 20:25:30 -0400, Dimi Paun wrote: > Go for it! We can see how well it works over the next couple of month. Done: http://wiki.winehq.com/ReleaseNotes

Re: Release notes

2005-05-24 Thread Dimi Paun
On Wed, 2005-05-25 at 00:43 +0100, Mike Hearn wrote: > Thoughts? Go for it! We can see how well it works over the next couple of month. -- Dimi Paun <[EMAIL PROTECTED]> Lattica, Inc.

Release notes

2005-05-24 Thread Mike Hearn
Hi guys, Raphael pointed out on IRC that the great OpenGL work that went into the last release wasn't mentioned in the "What's new" list that goes out with each snapshot. As it's unreasonable to expect Alexandre to remember or mention every large piece of work that goes into any given release, ho