[Uml-devel] Another Beta in some days?

[Luis De la Parra Blum]

I think we should fix the bugs and make the final touches and then make a RC 
(release candidate). Hopefully there will be no furhter issues with this RC, 
so we can rename it to 1.1

then I would suggest to make a branch Umbrello_1_1 and start with the next 
major version in head. 1.1 would be then officially closed, and there would 
only be, maybe a couple of releases 1.1.1, 1.1.2 if we get (easy to fix) bug 
reports after the release. (which hopefully wont be the case because we have 
ironed all the bugs out =)

>
> 637924: [PATCH] build erros on redhat 8.0
> Another lex/configure problem, I can't really say if we should accept the
> patch.
I'm getting tired of this problems... unfortunatlly I dont have RH so I cannot 
test it -- I think this should be part of the tests to do when we have the RC
--> download and install, just as a normal user would do, on all the systems 
we can get acces to, and make sure the build systems works.

> 637656: graphical class selection when boxes are
> Well, I don't know what the user wanted to tell us. I think if he didn't
> come back in some days to give a better description we should close the
> report. Or do you understand the report?

I'm not sure either... I *think* what he means is that all classes have the 
same "z" value, so if you first create class A and *then* create class B, and 
you move class A and put it ontop of class B, the user wants that class B is 
on Top (because it was created later)... now all classes have the same "z" 
value, so I guess the class you last moved gets drawn over the other 
classes...

could you try to contact the user and ask him what he means? if he doenst 
answer I would say we reject the report.


>
> 625869: assoc. not drawn correctly
> I think we found out that solving this problem isn't possible at the
> moment. So we have to wait for the redesign to solve this problem.

I am thinking it *could* be possible to make a hack around it.... but it 
woulnt be too nice:  doing a 
canvas()->invalidateAll()
canvas()->update()
after each draw operation..... I think this would fix this, but it would be 
very inefficient.
maybe someone can try this in his private copy and report about it ??

luis