Hi Bob, I'd prefer a "more clean" solution, too. Without EUML, this fix is not needed and would have no effect. A P2 in the module subsystem should indeed block a release, but obviously not this particular one. On the other hand, P2 is appropriate when it comes to UML2 support, so I'd be against lowering prio here.
What we need is a classification of issues that cannot block the release. Model/EUML is not enough, because not every UML2/EUML related change will happen in the EUML subsystem, but also in the core. So what do you think of defining a new component where such issues go into, and which will not block the release? Other alternatives: * simply fix that issue, for we are sure that this case will not happen again * set target to 0.31.1 and consider this when selecting blocking issues Thomas -------- Original-Nachricht -------- > Datum: Tue, 19 Jan 2010 10:01:20 +0000 > Von: Bob Tarling <[email protected]> > An: [email protected] > Betreff: Re: [argouml-dev] The release 0.30 is approaching - first alpha > planned for tomorrow evening > > Regarding 5836: I'd leave it P2 but assign it to Model/EUML > > I see your reasoning but not sure I agree with this. Where we assign > to a subcomponent it should be because a change is required in that > subsystem. For this the change is not required in the euml subsystem. > > Bob. > > ------------------------------------------------------ > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2440194 > > 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]] -- Preisknaller: GMX DSL Flatrate für nur 16,99 Euro/mtl.! http://portal.gmx.net/de/go/dsl02 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2440235 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]]
