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 *expecti
On Sun, 28 Dec 2008 09:10:29 -0800, Martin Aspeli
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 the final say in
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
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
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
On Sat, 27 Dec 2008 10:16:15 -0800, Ross Patterson
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 Norse
slœgð.[3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ross Patterson wrote:
> Tres Seaver writes:
>
>> Ross Patterson wrote:
>>> Tres Seaver writes:
>>>
Hanno Schlichting wrote:
> - Plone 4 will have a documented upgrade story
>
> A migration from Plone 3 to 4 does not need to be
Tres Seaver writes:
> Ross Patterson wrote:
>> Tres Seaver 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 ensure we have an
Hanno Schlichting
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 something more than
per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ross Patterson wrote:
> Tres Seaver 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 en
Tres Seaver 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 ensure we have an easy to
>> follow and understandable documented upgrade story.
On Dec 25, 2008, at 8:48 PM, Tres Seaver wrote:
If someone wants to champion bringing transmogrifier and GSXML up
to a
point where they are a fully-featured export and import story for all
aspects of typical Plone content types, that'd be awesome.
I have on tap a non-XML serialization which
Graham Perrin wrote:
> On 25 Dec 2008, at 17:08, Hanno Schlichting wrote:
>> Comments? Anything else people want to know at this point?
>
> One question and one suggestion. Responses -- from the Team, not
> necessarily from Hanno -- need not be 'at this point', January some time
> will be fine.
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
>
> 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 ensur
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
-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 document
16 matches
Mail list logo
