Release plans

[Tom Wickline]

On Sun, May 9, 2010 at 7:02 AM, Dan Kegel <dank at kegel.com> 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 it would take a lot more than that to fix them
> all, and it probably doesn't make sense to hold up the release until
> it's perfect.
>
> We probably want to update
> http://wiki.winehq.org/WineReleaseCriteria
> with the current release criteria.
>
> Some other interesting searches:
>
> Bugs marked as 'regression' (340!):
>
> http://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&keywords_type=allwords&keywords=regression
>
> Bugs marked 'bisected':
> http://bugs.winehq.org/buglist.cgi?quicksearch=bisected
>
> Anything A.F. has analyzed :
>
> http://bugs.winehq.org/buglist.cgi?product=Wine&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emaillongdesc2=1&emailtype2=substring&email2=focht
> - Dan
>
>
> 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. :)

--
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20100509/075e6658/attachment.htm>