On Wed, Dec 02, 2009 at 11:34:36AM -0500, Will Coleda wrote: > I would also recommend that we take over next week's parrotsketch for > the same type of meeting, to conduct any last minute steering in time > for 1.9 and 2.0).
I'm very worried about this part of the proposal -- I think the issues we have at present are too large to be adequately addressed in a 1-hour IRC meeting next week. Preparing the roadmap at PDS 2008 took us a lot longer than that (1.5 days of in-person meetings), and I think many of the issues today -- especially with respect to possible policy and procedure changes -- will need as much discussion this year as they did then. This isn't to say we can't use #parrotsketch to work on the roadmap... just that I don't think that it will be nearly adequate for Parrot's planning needs. Speaking a little more broadly, I think that holding planning meetings /after/ a supported release is getting things in the wrong sequence. When a supported release is issued, we should _already_ have our detailed plan in place for the next supported release, so that we're sure to have included any deprecations that are likely to occur and so that the Parrot user community knows what to expect in the next supported release. Pm _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
