I'm pretty sure that when I was debugging the P1 problem yesterday that the New Sequence Diagram button was creating sequence2 diagrams. This needs to be fixed if you're going to remove them from the build. Last minute changes like this are very high risk.
Tom On Sun, Jun 22, 2008 at 9:43 AM, Linus Tolke <[EMAIL PROTECTED]> wrote: > Sure, we can do that. > > I have implemented a solution to the Java Web Start problem, at least for > all other modules. > > Shall I remove the seq2 module from src/argouml-build/build.xml so that it > won't be pulled into the release? > > /Linus > > > 2008/6/22, Bob Tarling <[EMAIL PROTECTED]>: >> >> The limited testing means that we simply do not know the seriousness >> of the bugs. It seems that it just has not had enough testing for >> these to come out in the past and we're discovering them very last >> minute. >> >> While we have seq2 defects existing then the temptation is for me to >> look at those rather than the other P1/P2 defects and so you could say >> a final release is already being delayed seq2. >> >> Christian should be concentrating entirely on this years GSOC project >> so I wouldn't want to see him distracting himself with seq2 defects at >> the moment. >> >> I would suggest that the next release should be the first alpha >> release (ie no more enhancements allowed after that point) and we >> should concentrate only on our defects and getting the final release >> out. >> >> However could we consider to be a P2 defect anything that won't allow >> a module release of seq2 at a later date? >> >> e.g. >> 1) provide a listener to detect end of project load (probably >> registered with PersistanceManager) >> 2) Solve the problem of including seq2 when running with JWS. >> >> We can then release 0.28.1 at any future date when se2 is considered >> stable with no other changes to ArgoUML base, only the module >> included. >> >> Bob. >> >> >> 2008/6/22 Linus Tolke <[EMAIL PROTECTED]>: >> > Well, yes. I will let you and most notably Christian have the last say >> > in >> > this. >> > >> > I think the benefit of showing a new implementation could even out the >> > drawbacks of the limited testing performed on it. It is all in the >> > seriousness of the bugs and to what extent they can be fixed in time for >> > the >> > release and that is for you and Christian and everyone else involved in >> > the >> > testing and fixing to decide. >> > >> > /Linus >> > >> > >> > 2008/6/22, Bob Tarling <[EMAIL PROTECTED]>: >> >> >> >> What is your take on the seq2 situation? I presume based on most >> >> recent conversation that that will be withdrawn from this release. >> >> >> >> Bob. >> >> >> >> >> >> 2008/6/21 Linus Tolke <[EMAIL PROTECTED]>: >> >> > Since the issue 5151 is a P1 issue that is not resolved yet, I will >> >> > not >> >> > make >> >> > the 0.25.7 release today. Is there a plan for this issue to be >> >> > solved? >> >> > >> >> > /Linus >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> 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]
