Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases

2010-05-26 Thread Andreas Zeidler

On 23.05.2010, at 17:09, Hanno Schlichting ha...@hannosch.eu wrote:

#10365 / #10366 - @@blob-file-migration fails on migrated site


I fixed both of these today - but they are in desperate need of
testing on real world data sets :)


i haven't looked at the changeset itself ((In [36715]) Add upgrade  
step to convert all files and images to blobs.), but it sounds like  
the automatic blob-migration we didn't want to enforce.  existing file  
and image content should remain untouched and migration to blobs  
optional.


cheers,


andi

--
from phone — please excuse brevity___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases

2010-05-26 Thread Hanno Schlichting
On Wed, May 26, 2010 at 8:22 PM, Andreas Zeidler a...@zitc.de wrote:
 i haven't looked at the changeset itself ((In [36715]) Add upgrade step to
 convert all files and images to blobs.), but it sounds like the automatic
 blob-migration we didn't want to enforce.  existing file and image content
 should remain untouched and migration to blobs optional.
 cheers,

Why wouldn't we want to migrate content by default? If we don't do it
by default, only a few will figure out how to do it and people loose
the major advantage that blobs give them.

I haven't been involved in the PLIP discussions around this as much,
but I thought this was a clear case of something that just wasn't done
yet. If you have a specialized need, you can opt-out of this upgrade
step by using the portal_setup upgrades screen and omitting this one
step. But the default should be to migrate people.

Hanno
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases

2010-05-26 Thread Alexander Limi
On Wed, May 26, 2010 at 12:09 PM, Hanno Schlichting ha...@hannosch.euwrote:

 Why wouldn't we want to migrate content by default? If we don't do it
 by default, only a few will figure out how to do it and people loose
 the major advantage that blobs give them.

 I haven't been involved in the PLIP discussions around this as much,
 but I thought this was a clear case of something that just wasn't done
 yet. If you have a specialized need, you can opt-out of this upgrade
 step by using the portal_setup upgrades screen and omitting this one
 step. But the default should be to migrate people.


+1. Also, getting this change in as early as possible will give us more time
to figure out whether there are migration issues.

Having some data stored one way, and some data stored another (for the same
type of content) just seems like it'll cause problems later.

Is it a lot of work to enable? I assume the difficult part already exists,
since we can manually trigger the migration?

-- 
Alexander Limi · http://limi.net
___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team


Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases

2010-05-26 Thread David Glick
On 5/26/10 7:25 PM, Alexander Limi wrote:
 On Wed, May 26, 2010 at 12:09 PM, Hanno Schlichting ha...@hannosch.eu
 mailto:ha...@hannosch.eu wrote:

 Why wouldn't we want to migrate content by default? If we don't do it
 by default, only a few will figure out how to do it and people loose
 the major advantage that blobs give them.

 I haven't been involved in the PLIP discussions around this as much,
 but I thought this was a clear case of something that just wasn't done
 yet. If you have a specialized need, you can opt-out of this upgrade
 step by using the portal_setup upgrades screen and omitting this one
 step. But the default should be to migrate people.


 +1. Also, getting this change in as early as possible will give us
 more time to figure out whether there are migration issues.

 Having some data stored one way, and some data stored another (for the
 same type of content) just seems like it'll cause problems later.

 Is it a lot of work to enable? I assume the difficult part already
 exists, since we can manually trigger the migration?
If I recall, the main risks are that the migration may take a long time,
and that the admin may not have properly configured blob-storage in
their buildout.  The migration itself is pretty well-tested, at least
under Plone 3 -- Groundwire has migrated dozens of sites to use blobs. 
There may be some other concern I am forgetting?
David

--
David Glick
Web Developer
Groundwire
206.286.1235x32
davidgl...@groundwire.org
http://groundwire.org

Sign up for Groundwire News!  
 Tips, tools and news delivered directly to your inbox.
 http://groundwire.org/news-signup


___
Framework-Team mailing list
Framework-Team@lists.plone.org
http://lists.plone.org/mailman/listinfo/framework-team