Hi Linus Are you happy with the work so far?Any chance of completing similar for sequence2?
Once that is done the "Bugs blocking a release" link at http://argouml.tigris.org/dev.html can be updated to http://argouml.tigris.org/issues/buglist.cgi?Submit+query=Submit+query&issue_type=DEFECT&component=argouml&component=website&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&priority=P1&priority=P2&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time Actually I just realise this should be renamed to "Bugs blocking a final release" Bob. 2008/7/6 Linus Tolke <[EMAIL PROTECTED]>: > That sounds like a good idea. > > In that case the argouml component would be for subsystems and modules > included in the official releases. The new component would be for subsystems > and modules not included in the official release (yet). This should be > reflected in the chosen name. For immature projects, I have previously > choosen the project seeds to reflect the immaturity. There is a fairly good > correspondence between projects in the seeds subproject and not included in > the official release. > > The subcomponents to move are: > > AndroMDA module > Graphviz > Java support > Model/EUML > Model/NSUML > Python > Ruby > Sequence2 Diagram > > There is a practical problem in that a subcomponent can not be moved to > another component. This means that to create a move, I need to: > > Create the new subcomponent in the other component. > Move all issues (resetting version and target milestone) > Delete the old subcomponent. > > With the change-several-issues-at-once function this is easy to do but > notifications will be sent out on all involved issues when this is done. > > I will try this on the Model Element Property Panel subcomponent and let us > review the consequences before I continue with the others. > > /Linus > > 2008/7/6 Bob Tarling <[EMAIL PROTECTED]>: >> >> Linus has just created the Model Panel subproject for Christian latest >> GSOC project. >> >> How about creating a Sandbox component (choose a better name if you >> wish) and moving the Sequence2 Diagram and Model Panel subcomponents >> under there. >> >> That would make searching the argouml component in IZ cleaner and simpler. >> >> We can move subcomponents from sandbox to argouml when we have made a >> decision to release. >> >> Bob. >> >> 2008/6/30 Linus Tolke <[EMAIL PROTECTED]>: >> > I midded to update that link when I included seq2 in the release, but >> > that >> > is another story. ;-) >> > >> > /Linus >> > >> > >> > 2008/6/29, Bob Tarling <[EMAIL PROTECTED]>: >> >> >> >> If you look on the developers page you'll see a link called "Bugs >> >> blocking a release" which will show all P1/P2 defects that are not >> >> seq2. >> >> >> >> Bob. >> >> >> >> >> >> 2008/6/26 Thomas N. <[EMAIL PROTECTED]>: >> >> > Hi Linus, >> >> > >> >> > ok understood. Sorry for not being aware of that discussion. >> >> > >> >> > Thomas >> >> > >> >> > -------- Original-Nachricht -------- >> >> >> Datum: Thu, 26 Jun 2008 17:06:55 +0200 >> >> >> Von: "Linus Tolke" <[EMAIL PROTECTED]> >> >> >> An: [email protected] >> >> >> Betreff: Re: [argouml-dev] P1+P2 issues for Sequence2 subsystem >> >> > >> >> >> Hello! >> >> >> >> >> >> I think Bob and I had this discussion a couple of weeks back. I just >> >> >> went >> >> >> with Bobs suggestion in >> >> >> http://argouml.tigris.org/servlets/ReadMsg?list=dev&msgNo=22330 >> >> >> because >> >> >> that >> >> >> felt like the natural thing to do. You seem to be having the same >> >> >> thought >> >> >> so >> >> >> I see no conflict. >> >> >> >> >> >> /Linus >> >> >> >> >> >> >> >> >> 2008/6/25, Thomas N. <[EMAIL PROTECTED]>: >> >> >> > >> >> >> > Hi, >> >> >> > >> >> >> > Tom and I recently had an issue regarding the prio value for >> >> >> > issues >> >> >> > of >> >> >> the >> >> >> > Sequence2 Diagram subsystem. Since seq2 will not be included in >> >> >> > 0.26, >> >> >> it's >> >> >> > issues will no longer block the release. >> >> >> > >> >> >> > Question: Does this mean, that all seq2 issues should have a prio >> >> >> > not >> >> >> > higher than 3? Or can they have any prio and they simply will not >> >> >> > be >> >> >> > counted? >> >> >> > >> >> >> > (I vote for the second option, because there ARE more important >> >> >> > seq2 >> >> >> issues >> >> >> > and otherwise we would punish seq2 for not having its own >> >> >> > bugtracking >> >> >> > repository.) >> >> >> > >> >> >> > I'd like to have a decision from Linus how to handle this, >> >> >> > whatever >> >> >> > it >> >> >> will >> >> >> > be. >> >> >> > >> >> >> > Thomas >> >> >> > -- >> >> >> > GMX startet ShortView.de. Hier findest Du Leute mit Deinen >> >> >> > Interessen! >> >> >> > Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] >> >> >> > >> >> >> > >> >> >> > --------------------------------------------------------------------- >> >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >> >> >> > >> >> > >> >> > -- >> >> > Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! >> >> > Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer >> >> > >> >> > --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
