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
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
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
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
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
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
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
On Sun, May 23, 2010 at 4:09 PM, Hanno Schlichting ha...@hannosch.eu wrote:
#10365 / #10366 - @@blob-file-migration fails on migrated site
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
I fixed both of these today - but they are in desperate need of
testing on real world data sets :)
Gah, bad quoting. I fixed #10365 / #10366. David fixed #10549.
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
Op 20-05-10 22:00, David Glick schreef:
On 5/20/10 12:58 PM, Eric Steele wrote:
The main issues I'd like to see fixed and released before we move to RC are:
#10124 - should remove Large Plone Folder type and expose the folder
ordering setting in the schema
I have started working on this one.
#10360 - Incomplete migration: site_properties and portal_controlpanel
#10363 - Can not edit personal information when one is loged in with email
address
I fixed this one. Feel free to assign any remaining emaillogin related
tickets to me.
#10365 / #10366 - @@blob-file-migration fails on migrated site
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
--
Maurits van Rees
Programmer, Zest Software
___
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 5/20/10 12:58 PM, Eric Steele wrote:
The main issues I'd like to see fixed and released before we move to RC are:
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
Fixed.
--
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
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
I need to do some backtracking on my previous release plans...
First and foremost, I've completely overestimated the time I'd have available
this week. Preparing for next week's symposium has eaten all of my available
time and I'll be unable to cut a b4 beforehand. I absolutely hate being the
point of failure here, but we can make this work...
I'm now realizing I've put the cart before the horse on scheduling the first
RC. As Hanno points out, we have a number of yet-to-be-completed migration
issues that need to see the light of day in at least one release prior to an
RC. There are plenty of other bugs of all sizes to take care of as well.
The main issues I'd like to see fixed and released before we move to RC are:
#10124 - should remove Large Plone Folder type and expose the folder ordering
setting in the schema
#10360 - Incomplete migration: site_properties and portal_controlpanel
#10363 - Can not edit personal information when one is loged in with email
address
#10365 / #10366 - @@blob-file-migration fails on migrated site
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
We also have scads of finishing touches to make to templates/CSS, including 7
open tickets regarding Alex's introduction of CSS sprites. There are another 23
open tickets relating to TinyMCE. I also need to consult with Sidnei regarding
some concerns over the Windows installer.
As always, there is a full list available to those wishing to try their hand at
the rest. http://tr.im/plone4tix
So let's move the b4 release to June 2, which should give us time to get the
majority of these wrapped up (and provide me with the time to actually cut the
release). At that point, I'll take another look at what's remaining and decide
whether a June 16 release should be dubbed b5 or rc1.
With Jessica's blessing, I'm proclaiming the upcoming May 28th TuneUp an
official Plone 4 bug day. I'd appreciate help in spreading the word.
Thanks,
Eric
___
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 5/20/10 12:58 PM, Eric Steele wrote:
The main issues I'd like to see fixed and released before we move to RC are:
#10124 - should remove Large Plone Folder type and expose the folder ordering
setting in the schema
I have started working on this one.
#10360 - Incomplete migration: site_properties and portal_controlpanel
#10363 - Can not edit personal information when one is loged in with email
address
#10365 / #10366 - @@blob-file-migration fails on migrated site
#10549 - Uncaught NotFound exception in plone.app.linkintegrity when page
contains some @@{view} links
--
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
Re: [Framework-Team] [Plone-developers] Upcoming Plone 4.0 releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Steele wrote: snip So let's move the b4 release to June 2, which should give us time to get the majority of these wrapped up (and provide me with the time to actually cut the release). At that point, I'll take another look at what's remaining and decide whether a June 16 release should be dubbed b5 or rc1. Sounds like a good call to me. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkv1rOsACgkQ+gerLs4ltQ6LGACgk9iCf915EQrHUV+qayxurXBk KM0AoJq6WEfCB9JZV/Ty5Iu5KrAWolC3 =vhON -END PGP SIGNATURE- ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
