RE: [argouml-dev] The upcoming 0.21.3 release

[Linus Tolke]

Title: Message

Thanks Tom for the explanation…   I think that 0.21.3 is a pressing matter. I will start planning it for tomorrow and hoping that we can resolve this.   You are right that we need to address all the P2 defects soon. I would like to say that I think the biggest mistake I made with the planning of the 0.20 release was to enter the alpha/beta phase with lots and lots of P2 defects. Since I consider all betas to be more or less release candidates I think it is a good idea to require that there are no P2 defects in any of the beta releases, maybe also for the alpha releases.               /Linus   From: Tom Morris [mailto:[EMAIL PROTECTED] Sent: den 5 juni 2006 19:45 To: dev@argouml.tigris.org Subject: RE: [argouml-dev] The upcoming 0.21.3 release   I think the quality guidelines are being followed in most cases ie. the P1s are project corrupters.  Most of the ones that I've seen recently have been duplicate reports of already fixed bugs in 0.20.  Our release criteria aren't really set up to handle this case, so I think a little human judgement needs to be applied.  We planned a short schedule for this release specifically to address serious problems introduced by the huge amount of new code in 0.20.  Issue 4110 http://argouml.tigris.org/issues/show_bug.cgi?id=4110 is just such a problem, so it would really be nice to get it fixed for users.  So far it's been reported 5 times and who knows how many more projects it's corrupted that we don't know about.  I think there may be one or two P1 PGML problems that have been reported multiple times as well.   The P1 that was opened today is one of the rare ones that I don't think is really a P1 (ie it doesn't cause any loss of data).  It does however point out an area where we've (intentionally) destablized this release.  In retrospect I should have fought harder against completely changing the MDR exception handling during a release who's entire theme was stabilization and bug fixing, but that's water under the dam.    Just behind the P1s is a set of  a dozen P2s that our release criteria say will need to get resolved to release 0.22.  Since we've got a very short alpha/beta period scheduled, those really need to be addressed now as well.  Some of them are probably mis-prioritized, so they need some triage.   I'm pretty sure that "waiting for this to subside" won't work.  This needs to be actively managed if we want to have any hope of getting this release done in a timely fashion.   Tom   -----Original Message----- From: Linus Tolke [mailto:[EMAIL PROTECTED] Sent: Monday, June 05, 2006 7:23 AM To: dev@argouml.tigris.org Subject: [argouml-dev] The upcoming 0.21.3 release Hello all!   Every time I look there seems to be new P1 issues created. This is not reassuring at all but I have just been waiting for this to subside.   What is going on? Why is this happening? Have we put the quality level higher this time?   What shall we do? What can I do?               /Linus   ******************************************************************* Linus Tolke  [EMAIL PROTECTED] *******************************************************************