Hello again Bob!
I think many of the problems were small problems with information getting
lost in the save and restore cycle for diagram information. Tom mentioned a
couple of months ago that there is a big need for testing this and I made a
feeble attempt at creating a JUnit test but didn't manage to get it working.
For the future, where are we going with the save and restore for diagram
information? Are we contemplating the di2 and MDR to replace the pgml?
/Linus
2009/3/19 Bob Tarling <[email protected]>
> Immediate thoughts are -
>
> Not enough of junit tests.
>
> Not enough physical separation of the application into modules.
>
> A small team so not enough manual testing.
>
> Old problems with poor threading now catching up on us.
>
> Lack of resource.
>
> Lack of specific required skills.
>
> Bob.
>
> 2009/3/19 Thomas Neustupny <[email protected]>:
> > 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]]
> >
>
> ------------------------------------------------------
>
> http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1355825
>
> 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]]
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1357910
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]]
