Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
David Glick wrote: [..] 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? The only other concern I recall is the potential breakage of backup routines. If someone just rsyncs/copies Data.fs via cron (or the like) it will miss the binary data after the upgrade. Raphael ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5/27/10 10:03 , Raphael Ritz wrote: David Glick wrote: [..] 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? The only other concern I recall is the potential breakage of backup routines. If someone just rsyncs/copies Data.fs via cron (or the like) it will miss the binary data after the upgrade. As someone who wears two hats (developer and admin) I can see both sides. However, my admin side is always upset about potentially unknown upgrade consequences. As a compromise I would suggest an upgrade experience where the user gets something pushed into their face about admin changes that may need to happen before they push the button. As long as people are made *very* aware of the change *and* they have the opportunity to stop the upgrade at that moment to prepare their systems it would be OK. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkv+KoIACgkQRAx5nvEhZLJltwCgjVLlv38kJA2kCGqxAoktB5Rz xvwAnR6zvhyhjmkH2rfAZrNgNYlvheuT =YhoW -END PGP SIGNATURE- ___ 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
On Thu, May 27, 2010 at 10:03 AM, Raphael Ritz raphael.r...@incf.org wrote: The only other concern I recall is the potential breakage of backup routines. If someone just rsyncs/copies Data.fs via cron (or the like) it will miss the binary data after the upgrade. We are migrating the types to use blobs in any case. So any new images or files he adds are going to go into blobstorage and would be missed. This is only about existing content. People have to change to a completely new zeoserver recipe, which creates a blobstorage by default. So the risk of having no blobstorage and getting an error is fairly low. Maybe there can be better documentation in the upgrade guide for the backup related changes, but those are needed in all cases. Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
