We seem to have lost our focus on making this a quick turnaround release to fix critical problems in 0.20.
I was all for this but I'm not sure that all devs bought into this at the time.
My impression is that many (most? all?) of these late breaking problems are bugs that we introduced during this development cycle.
That does seem to be the case. I accept some of that responsibility by modifying the GUI to act correctly on model element delete events. However as a result of this we found the cause of several persistence problems.
I would like to see the next beta be our last. This means we've got to be 100% focused on stability. As far as additional AndroMDA stuff goes, I'm a big AndroMDA supporter, but we can only have a limited number of #1 priorities. We defered work on issue 4031 which would be a substantial benefit to AndroMDA users and I think issue 4318 is going to have to fall into the same category unless it turns out to be an absolute show stopper (I'll investigate and update the bug report).
Great - as I said I'm not sure how well founded my concerns are. It needs a decision from someone familiar with that usage.
One other schedule thing - it makes most sense to me to do the SVN upgrade at a release boundary. Is there a reason that we have it scheduled for partway through the next development cycle? Can we move it to immediately after the 0.22 release?
I think the date was set to avoid any configuration problems that may plague our students during their last phase of work. There is only Andreas work going to head at the moment with Michiel commiting so that does limit the problem but I'd prefer my student remained focused on his task rather then stop to setup and configure eclipse to get updates through some other mechansim. Or even worse suffered downtime should anything go wrong at the tigris end during the conversion. Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
