Hi all, I think we all appreciate all the work Linus is putting into this, but is it necessary to have this very strict schedule? We are only piling up the releases. IMHO we should first solve the issues and then make a beta release. And even with the alpha releases, having a new one only because very few things have changed and because the schedule dictates it to is a waste of Linus' time. Did we really needed 5 alpha releases? I believe we should be more flexible on this and give more general release dates (beginning, middle, end of the month) at least for the first releases where the time is not known precisely, and only announce a the later releases with more precision. I'm not saying to drop the schedule, but to have more flexibility on it. Because after all, having a schedule but never meeting the deadline is not having a schedule.
Regards, Bogdan Linus Tolke wrote: > Hello all! > > We are now up to 8 open P2 defects blocking the release. It is > disturbing that the amount of issues is not decreasing as I was > hoping. What shall we do? Where shall we go from this? > > Yet another alpha release before the beta and stable release is the > minimum in the planning of the release but what shall we do to get > there? Personally, I know my limits in understanding the coding > problems we are facing so I must ask you all to work together on this. > > I will make a new plan including the new alpha release moving > everything forward, that is what I can do in the planning. How do we > proceed before the 0.28 stable release? What shall we do after the > 0.28 release to avoid this kind of problems again? > > /Linus > > 2009/1/30 Linus Tolke <[email protected] <mailto:[email protected]>> > > Hello all! > > There are still 6 open P2 defects blocking the beta release. I > will monitor the issues and attempt to make a release on Sunday > instead. > > /Linus > > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1085836 To unsubscribe from this discussion, e-mail: [[email protected]].
