I think adding a little time to the beta period is a good idea, but I'm VERY concerned that we maintain the discipline necessary to stabilize this release by not shoehorning more "nice to have" stuff into it. This release was planned for May 15 (not the "original planned date" of July 21 that's on the web page). A beta on Aug. 8 would imply a release date of Aug. 15 or later. That's a 3 month slip on a 3 month schedule -- 100%!
We seem to have lost our focus on making this a quick turnaround release to fix critical problems in 0.20. My impression is that many (most? all?) of these late breaking problems are bugs that we introduced during this development cycle. 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). 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? Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
