[Framework-Team] Re: [plone4] Release process
me at rpatterson.net
Sat Dec 27 06:40:35 UTC 2008
Tres Seaver <tseaver at palladion.com> writes:
> Hanno Schlichting wrote:
>> - Plone 4 will have a documented upgrade story
>> A migration from Plone 3 to 4 does not need to be possible in an
>> almost fully automated fashion. We need to ensure we have an easy to
>> follow and understandable documented upgrade story. If we for example
>> change API's or rearrange code, we can document the new places in
>> writing and with error references for the most commonly used
>> parts. If you need to change your buildout configuration, a document
>> explaining the changes is fine, we don't need to build an upgrade
>> machinery for configuration files.
> Can I persuade you and the FWT to forego an "upgrade-in-place"
> strategy for moving from P3 to P4, and instead to have a well-tested
> ad documented "dump-and-reload" story?
I've never actually understood how a dump-and-reload approach would be
inherently more maintainable or otherwise more trouble-free. I know
this has been discussed before, but I missed those discussions. Can
anyone shortcut the research for me and give me some links or pointers
to previous discussions?
More information about the Framework-Team