>
>
> > I'd nominate the incumbent 3.x team for this; this team already has
> > the mindset to get this going; the future plone team (trunk team?) is
> > focusing on vision right now, which I think may not be what's needed
> > for an in-between team.
>
> On second thought; this may be a significant enough release, with it's
> own 4.x release series, that perhaps a new team altogether is
> warranted?
>
>
It would be a shame if the development of Plone trunk will get less focus
from the FWT when working on Plone 4. So it might indeed not be a bad idea
to have 2 teams, one team for Plone 4 and one team for Plone trunk.
--
Rob Gietema
Four Digits
_______________________________________________
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team

Reply via email to