What’s New in Opencore 0.13
The biggest changes in this release are:
- Plone 3 required!
- Many things are noticeably faster, because Plone 3 is faster than Plone 2.5.
- Lots of minor bugfixes and usability improvements
For more details, see CHANGES.txt in the opencore source.
This release also requires a data migration that is not backward compatible! Let me say that again:
This release requires you to run a data migration that is not backward-compatible.
Once you upgrade, you can’t go back.
Always Make Backups!
Ahem.
Also, if you have your own code that runs on top of opencore, you should plan on doing thorough testing and may need to modify your code to run under Plone 3.
How to Upgrade
First, make a backup of your ZODB.
Next, run a pre-upgrade migration as described here:
https://svn.openplans.org/svn/opencore/trunk/docs/Plone2.5-Plone3-migration.txt
Note that you need to be on Opencore 0.12.1 (or later, if we ever do an 0.12.2 etc.) to have that migration script available. So if you’re running an earlier version, you’ll need to upgrade to 0.12.1 first.
Then you’re ready to upgrade to 0.13. For this upgrade, I highly recommend leaving your old build alone in case something goes wrong, and create a new build from scratch in a parallel directory. As with previous releases, Opencore still doesn’t work via easy_install, you have to get it by checking out the tag from subversion: https://svn.openplans.org/svn/opencore/tags/0.13.0 and then install using python setup.py develop. You’d also have to install Zope 2.10 and our plone 3 Products tarball. Or use TOPP’s usual build tools which will do all that for you.
I highly recommend the latter approach, it’s a lot more convenient. We have requirements profiles ready for you to build:
- For a pretty stripped down opencore build (just Opencore, Zope, Zeo, and supervisor; no Tasktracker, no Wordpress, etc.), you can use these requirements: https://svn.openplans.org/svn/build/requirements/opencore-minimal/tags/opencore-0.13.0
- For a full-featured build like openplans.org, with wordpress and tasktracker and everything, you can use these requirements: https://svn.openplans.org/svn/build/requirements/openplans/branches/opencore-0.13
… although I’m not sure that’s the right place for that requirements set; Doug Mayle, the deployment manager, could overrule me and put it somewhere else. I’d suggest keeping an eye on https://svn.openplans.org/svn/build/requirements/releases where the final requirements are likely to show up once Doug does all his work to prepare for deploying to openplans.org. That would also be a good sign that we’re getting confident enough to deploy it ourselves
After you upgrade, you’ll need to run the post-upgrade migrations. Again, see:
https://svn.openplans.org/svn/opencore/trunk/docs/Plone2.5-Plone3-migration.txt
Start things up and you should be all set!
Special Thanks
The Plone 3 porting was almost entirely performed by Rob Miller. It was a big job, thanks Rob for moving us forward!
Support
As always, if you have any problems, contact us on the opencore-users mailing list or look us up on the #openplans IRC channel on freenode.
I will be on vacation until 2008/08/25. Good luck while I’m gone
– Paul Winkler