Hi Linus, you were asking questions that run through my mind, too.
Linus wrote: > How do we know that we have seen the end of these? We can't. It depends on the intensivity of (the voluntary) testing. I had not the time to test all diagrams until last week. We simply seem not to be fast enough to get this software tested in a reasonable time. It's just that we can't speed up quality assurance activities, because we suffer from testing ressources and can't overcome it by just demanding it. Personally, I'm now almost through with my tests, so (hopefully) no more findings from me. ;-) > And... what is it that we did since the 0.28 > release that has made all these problems appear? I guess you mean 0.26. Well this makes me crazy, too! Suddenly things got broken that worked well before, and in most cases we don't know why. And no analysis on that. And still ArgoUML sometimes behaves weird (e.g. Quit->WannaSave?->Yes->SavingButNotQuitting, or the deselect-select workarounds) but I got used to it and don't dare to file an issue anymore for these minor things because of the huge amount of open (more important) issues. The team repairs for years now, and it's like fighting wind mills, and I don't now why. Is it GEF or a global architectural problem? Or is it normal for software of this size? Don't know, but keeps us from further developing ArgoUML. Thomas -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1355772 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
