Re: Date of 2.2 release.

msevior@physics.unimelb.edu.au wrote:

>Hi Folks,
>
>
<snip>

>One very significant change this year as opposed to last year when we
>released 2.0 is the much improved QA team we now have. You guys rock!
>
>The upshot of this great QA team is we now have lots more high quality bug
>reports than we had last year at our 2.0 release.
>
>
And a lot of good cleaning up of the rest of the data base, too.
Bugzilla spam is definitely showing some cleaning of invalids,
resolveds, dupes, etc, and I'm likin it!

>OK so the big question: What's the schedule?
>
>Well this is hard because I don't know how hard it will be to fix some of
>the bugs we have. I also don't know how many people will work on fixing
>them. I do know I don't want to wait too long for a 2.2 release.
>
>There are some absolute killer bugs that must be fixed before 2.2.
>
>There are:
>
>1. Slowness of typing on OSX.
>2. No TOC dialog on OSX
>3. No Stylist dialog on OSX.
>4. No Fold Text dialog on OSX.
>5. No TOC dialog in windows
>6. No Fold Text dialog on windows.
>
>IMHO these are cirtical for 2.2. We won't release until these are in place.
>
>
>
Oh yes! Windows definitely needs those dialogs. Wouldn't hurt if the
MingW build was fixed too, since it's really hindering my ability to
test, since I don't have MSVC.

Printing becoming unbroken would also be good.

>So the upshot of this is that I think we can seriously aim for a 2.2
>release on August 31st. I feel confident we will have a wonderful program
>that we can all be proud of by then. I'm certain that we will still have
>bugs on August 31st but there is a good chance they will be small enough
>that we can live with them.
>
>What do people think?
>
>
I think it's a good goal, but a tad optimistic on Windows. I've been
using it lately, and there are a fair amount of odd crashers that must
sort of "build up", since the simple act that appeared to cause them
works fine when you try to reproduce.

Additionally, windows printing (for me at least), is completely broken.
(abi bug 6827, plus margins being weird, and other things ). I really
can't see an official Windows release with printing in this state, but I
don't know how well this will work out. I know there are few who are
familiar with Windows, Windows Printing, _and_ c++, but if there are any
of you reading the list and lurking, or whatever, I think the Windows
port could use a bit of your sweet coding lovin. That's about it on my
end, things are looking pretty good, just needs some polish!

>Cheers,
>
>Martin
>
>
Ryan
Received on Sun Jun 20 06:12:07 2004