I'm looking into 5969 and will then check 6008 and 6015. I have a situation where a created profile with 0.30 causes exceptions when used in a project and this makes the stereotypes and other extension mechanisms to fail. I'll try to open it after having an automated test for 5969.
My .02€ on 0.30.x: >From the perspective of the profile subsystem I agree that our users would benefit if 0.30 is shortly replaced. This might be the last stable release before UML2 brings in more instability and the risk of having a big period without a stable release. With Bob being currently the only core developer with a significant contribution rate there should be some focus on polishing this hypothetical last UML1.4x release of ArgoUML. Our current users deserve it - we included :-) Finally, I propose that we consider some P3 issues for inclusion in a 0.30.x release. My problem with some of these P3 issues is that although they are correctly classified as such, according to http://argouml-stats.tigris.org/documentation/defaulthtml/cookbook/ch09s02.html#issue_priorities, some of these "Functions not working" make ArgoUML barely usable in some contexts. For me, I have the P3 issues above and will probably stumble or rediscover some more. Regards, Luis On Wed, Mar 24, 2010 at 12:14 PM, Bob Tarling <[email protected]> wrote: > > I concentrated on putting back commands that are not available by > other means as being the highest priority. In subversion all tools are > now available in some fashion. > > I know Luis is also busy with the profiles/stereotypes problem so that > gives me a little time to see if I can improve things further by > adding new buttons by a single item list such as the guard for a > transition. I can also place a delete button back on the panel itself. > > I think we should still consider beta1 though so that the users see > this is improving. > > Bob > > On 24 March 2010 09:40, Thomas Neustupny <[email protected]> wrote: > > Hi, > > > > here is another report on a property panel related defect (deletion of > > guards in activity diagrams), which probably should be considered (I asked > > him to record it in issuezilla): > > http://www.argouml-users.net/forum/viewtopic.php?f=5&t=201 > > > > I must admit that I have no time to systematically check property panels > > for functionality loss (compared to 0.28.1), but I suspect there's more. So > > either this analysis should be done, or we should prepare for a nice little > > 0.30.x series of bug fix releases. :-) > > > > Thomas > > > > -------- Original-Nachricht -------- > >> Datum: Tue, 23 Mar 2010 07:04:44 +0100 > >> Von: Linus Tolke <[email protected]> > >> An: [email protected] > >> Betreff: Re: [argouml-dev] Release 0.30.1 > > > >> If we should add more fixes or not depends on how far we will wait before > >> making the release. We could make it now (i.e. tomorrow night or Thursday > >> night) or wait another week or so. > >> > >> I agree with you that the issue you noted is a good suggestion for things > >> that needs to be fixed and it looks like it is the only new issue that is > >> that important. Then the question is when this issue can be fixed. How > >> complicated is this? Luis? > >> > >> Shall we plan for this weekend? > >> > >> /Linus > >> > >> > >> On Mon, Mar 22, 2010 at 7:33 PM, Bob Tarling <[email protected]> > >> wrote: > >> > >> > I believe I've fixed all the outstanding issues with the new property > >> > panels and we should consider release phase soon. > >> > > >> > I believe there is no code commited since 0.30 that should not be > >> > included in this release. > >> > > >> > I wonder if it should be consider to include any further defects. In > >> > particular I noticed > >> > http://argouml.tigris.org/issues/show_bug.cgi?id=6008 and am concerned > >> > this may cause problems for users of profiles. > >> > > >> > Bob. > >> > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2464592 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]]
