[Framework-Team] Re: [plone4] Release process

Tres Seaver tseaver at palladion.com
Thu Dec 25 23:01:39 UTC 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJVBDT+gerLs4ltQ4RAqb/AJ424SE/qqstfmRvQ/pJKDisbbvRvgCgjVYw
E/XtFRo81n2SdHAU3m0ALnM=
=+vuy
-----END PGP SIGNATURE-----





More information about the Framework-Team mailing list