> > We've been spending a ridiculous amount of time trying to > migrate from > > 2.0.5 to 2.1.1 . > > This is a great shame because migration is a showstopper on what > > otherwise looks like an exciting new release with more > functionality > > and much better performance.
How about simply *paying* a company to do the migration for you? Hopefully the company you would pay would be involved with Plone enough to fix this error from happening and the next maintenance release of Plone 2.1.2 would have this fixed? > > I question whether the migration code was tested enough. It should > > have been tested on a number of Data.fs s from many > different users. > > This would have revealed fragilities, and bugs would have > been fixed > > before an official release, but I struggle to believe > enough of this > > happened, because otherwise there wouldn't be such problems. We had no problems with our systems upon migrating. Alan Runyan _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
