Re: [Framework-Team] Re: [plone4] Release process

2008-12-28 Thread David Glick
On Dec 28, 2008, at 5:37 PM, Martijn Pieters wrote: On Fri, Dec 26, 2008 at 23:19, David Glick wrote: I am definitely interested in seeing more work on filling out the holes in GS support in core Plone. If we include a tool for dump-and-reload content migration in Plone itself, I think i

Re: [Framework-Team] Re: [plone4] Release process

2008-12-28 Thread Martijn Pieters
On Fri, Dec 26, 2008 at 23:19, David Glick wrote: > I am definitely interested in seeing more work on filling out the holes in > GS support in core Plone. > > If we include a tool for dump-and-reload content migration in Plone itself, > I think it needs to be pluggable enough to be useful with non

[Framework-Team] Re: [plone4] Release process

2008-12-28 Thread Martin Aspeli
Hi Alex, Yup, the idea is to make AT *optional* (but still default), and to be able to supply a Dexterity-based alternative. Then we can work on the migration story from AT->Dexterity without that being a blocker for 4.0. In other words, if you start a new project, you'll probably want to l

Re: [Framework-Team] Re: PLIP lifecycle

2008-12-28 Thread Tom Lazar
On 27.12.2008, at 23:28, Alexander Limi wrote: On Sat, 27 Dec 2008 09:56:23 -0800, Ross Patterson wrote: One way to keep these cross-checks lightweight might be to start with a statement of impact. There are code changes, for example, that have no UI impact. In such cases, it would be