Here's my take on which bugs we must/should/ought to (try to) fix for the release, some of them because they're bad, some because they're relatively easy to fix or maybe already fixed. Those on Windows are marked correspondingly. Can everyone please go through the list and see if you can reproduce/add more details/report status/fix it/whatever? Help from Windows folks is especially appreciated.
WIN 1069560 - annoying and pretty frequent, does anyone has an idea of what's happening there?
1108667 & 1086769 - may be the same bug but may be not, I cannot check because I don't have these input methods installed
1107922 - may be fixed by now, but I never could reproduce it anyway
WIN 1107305 - something's wrong with Windows paths after Kees changed them. Need more details.
1102678 - need to force libxml to load external DTD (OK, I'll look at it once more, now that I have a newer libxml)
WIN 1095300 - need more info from windows folks, is it still there?
1093060 - an easy-to-run-into freeze, I upped priority to 9, must be fixed (Mental?)
WIN 1050361 - still can't open svgz on windows (again!)? It used to work, does anyone know what happened?
1055034 - do we now check for correct versions of libsigc? Can this be closed?
WIN 1070816 - I guess there's no progress on this one. Looks like we'll have to release with it again.
WIN 1073459 - This one frustrates me. It may be fixed but we can't figure out for sure yet. I asked about it before but got no definitive answer. Those who builds on Windows: Please check which version of libgc (boehm) you are using. If it is 6.4 AND you use latest CVS, see if you can reproduce this bug. If it's not 6.4, ask the person you got it from (Ishmal?) for this version. PLEASE LET'S CLOSE THIS ONE. It alone is worth a release.
WIN 1076627 - Jon Cruz is working on that, is there chance it will be fixed?
WIN 1068818 & 959352 - this may be the same bug or may be not.