On Thu, Apr 2, 2009 at 3:23 PM, Juergen Schmidt <juergen.schm...@sun.com> wrote: > Hi Mathias, > > Matthias B. wrote: >> >> On Wed, Apr 1, 2009 at 11:27 PM, Maximilian Odendahl >> <max.odend...@t-online.de> wrote: >>> >>> can you name some of these regressions which prevent you in using 3.1? >>> >> >> >> http://www.openoffice.org/issues/show_bug.cgi?id=100374 >> >> and >> >> http://www.openoffice.org/issues/show_bug.cgi?id=100718 >> > thanks for the info. Do you have more issues? Your former email sounds of > course much more worse.
I was referring to the past. There have been other bugs and backwards-incompatible changes in the past that broke things for us. For instance there was the backwards-incompatible change of the classloader, I think in 2.3. Then there was the backwards-incompatible change of the bootstrap mechanism with 3.0. The bugs I do not remember. We've reported 131 issues so far (according to my query). It's hard to keep track :-) Then there are things that we haven't reported because they cannot be reproduced reliably and there are more of those in 3.x than in earlier releases. For instance OOo 3.x sometimes freezes when I click into the UI "too soon". Furthermore OOo 3.x feels slower than 2.4. All in all, the quality seems to have gone done with 3.x. > Two issue, both submitted really late for a 3.1 release. That is not optimal > and of course it was really late. You have pointed out that you switched to > dev snapshots early but because of too much problems you moved back. Have > you reported problems at this time? No. When I get a segfault right away simply launching swriter I do not bother to report it. Same goes if OOo won't build in the first place (e.g. because of missing modules). These things are so obvious that they must be known. BTW, those were trunk builds. I think someone else has already mentioned that trunk should be kept somewhat stable. It makes people lose confidence if it doesn't even start up (or build). After all, the next version will be branched off from trunk. If trunk is broken, the next version will be initially broken. > I think it is important that you give us feedback or that you report > problems/issues asap so that we have time to address this problems. I don't > know if you have reported the problems earlier to somebody or if you have > simply ignored them until your latest evaluation. We report issues as soon as possible for us but you have to understand that filing quality bug reports with test cases (which we usually do) takes time. Issue 100718 has taken me a complete day to analyze and construct a test case for. I can't simply drop my regular work for a whole day whenever an OOo issue comes up. Especially when it's early in the OOo release cycle there's a strong motivation to just wait and see if the bug gets fixed. Again, the quality of trunk and early milestones is partially to blame. If I were under the impression that trunk/milestones are supposed to be of high quality, I would be more inclined to spend time examining bugs early. But since I'm under the impression that trunk breakage is normal, that merging buggy code is normal and that all in all it's normal that hordes of new bugs are introduced that won't be fixed until late in the release cycle, I think to myself: "Well, they know that their code is broken. There's no need for me to waste my precious time constructing test cases for bugs they are probably already aware of." Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
