[Framework-Team] Plone 3 - Migration supported for age-old versions?
Heya guys. I'm still working on my CMF 2.1 branches and came across quite some new problems all due to the migration machinery. As I'm lazy and don't want to debug and write code if it's not necessary, here is a little idea I would like to have some feedback for: Don't support migrating to Plone 3 from versions earlier then Plone 2.1.0-final. Why 2.1.0-final and not 2.1.0-alpha something? Because we changed to much in the 2.1.0-alpha/beta migrations and you shouldn't run any of these beasts in production anyways. What about Plone 2.5? Migrations from all insane alphas/betas/rcs should be supported. What do you think about it? My main point here is that I would like to save the time to debug all the possible issues of the CMF Types to ATCT migrations and I think supporting all these migration scenarios without any reasonable test infrastructure like we have now is close to insanity ;) As a side effect this will also save us from having to support any Zope 2.6 or earlier to Zope 2.10 migration scenarios :) We don't really do this right now, let's make that explicit. Hanno P.S. If I get some support for the idea, I'll write a full-fledged PLIP for it... and do one of my favorite things: remove some code :) ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: Plone 3 - Migration supported for age-old versions?
On Fri, 2006-09-06 at 17:06 +0200, Hanno Schlichting wrote: > Don't support migrating to Plone 3 from versions earlier then Plone > 2.1.0-final. My initial feeling about this was, "but this is what makes Plone so great, being able to migrate from Plone whatever to current". But then I thought about it some more and read more of your reasoning... the more I think about it the more insane I think it is to support a migration so far back. If the client wants to support a migration as old as that we could lay out documentation steps I supposed, "using zope 2.6 and plone 1.x do your upgrade to plone 2.0, then upgrade zope to 2.7 then do another upgrade to plone 2.1", etc etc. So I'm +1 on limiting the migration path we support in Plone 3.0. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
