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

2009-01-02 Thread Erik Rose
On Dec 27, 2008, at 13:31 , Ross Patterson wrote: It seems like this this dump format will likely become a point of hackability in our software ecosystem. People out there will find interesting things to do with it aside from dump-and-reload. This would be a good thing except we're

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

2008-12-29 Thread Alexander Limi
On Sun, 28 Dec 2008 09:10:29 -0800, Martin Aspeli optil...@gmx.net wrote: Please note that whilst this vision sounds more or less in line with what I hope will be possible and desirable soon, this is not something that's been decided. The 4.0 framework team and release manager will have

[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

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

2008-12-28 Thread Martijn Pieters
On Fri, Dec 26, 2008 at 23:19, David Glick davidgl...@onenw.org 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

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 davidgl...@onenw.org 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

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

2008-12-27 Thread Ross Patterson
Hanno Schlichting hanno...@hannosch.eu writes: - Plone 4 will be primarily a feature based release, not time-based ... - Plone 4 will be released based on an agile approach +1 I like this approach a lot. I've been worrying about how to be ambitious while still ensuring that Plone 4.0 is

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

2008-12-27 Thread Ross Patterson
Tres Seaver tsea...@palladion.com writes: Ross Patterson wrote: Tres Seaver tsea...@palladion.com writes: Hanno Schlichting wrote: - Plone 4 will have a documented upgrade story A migration from Plone 3 to 4 does not need to be possible in an almost fully automated fashion. We need to

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

2008-12-27 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ross Patterson wrote: Tres Seaver tsea...@palladion.com writes: Ross Patterson wrote: Tres Seaver tsea...@palladion.com writes: Hanno Schlichting wrote: - Plone 4 will have a documented upgrade story A migration from Plone 3 to 4 does not

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

2008-12-27 Thread Alexander Limi
On Sat, 27 Dec 2008 10:16:15 -0800, Ross Patterson m...@rpatterson.net wrote: So I would like to see something of a slight-of-hand here. Sleight. Just because I used to make the same mistake myself. ;) Speaking of Dexterity: Sleight, meaning dexterity or deceptiveness, comes from the Old

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

2008-12-25 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: - Plone 4 will have a documented upgrade story A migration from Plone 3 to 4 does not need to be possible in an almost fully automated fashion. We need to ensure we have an easy to follow and understandable documented

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

2008-12-25 Thread Hanno Schlichting
Tres Seaver wrote: Hanno Schlichting wrote: - Plone 4 will have a documented upgrade story A migration from Plone 3 to 4 does not need to be possible in an almost fully automated fashion. We need to ensure we have an easy to follow and understandable documented upgrade story. If we for