Should I upgrade?
This is a bugfix-only release. If you are running opencore 0.13 or 0.14, this should be a safe upgrade with a few useful fixes.
If you are still running opencore 0.12 or earlier on top of Plone 2.5, this is a fairly big upgrade; see the 0.13 announcement for more info.
What’s New Since 0.14.0
Data Migrations: You will need to run this migration only if you’re upgrading from 0.13 or earlier. You can run the migration via the portal_setup tool in the ZMI; go to the upgrades tab and run the upgrade registered for version 0.14.0.
Bug fixes:
* List manager address was showing up as escaped HTML. (slinkp) (http://trac.openplans.org/openplans/ticket/2706)
* Wiki version view doesn’t error when no version_id is specified (slinkp) (http://trac.openplans.org/errors-openplans/ticket/30)
* Error page doesn’t barf on 404s if the catalog has a problem coming up with suggestions based on the current URL (slinkp) (http://trac.openplans.org/errors-openplans/ticket/23)
* Fixed rare error in recataloging projects, raised by the project’s _default_img_data method. (slinkp)
There are also a bunch of upstream bugfixes in Listen, our mailing list component. You will want to upgrade if you’ve had any trouble with non-ASCII characters in mail messages.
How to Install
As usual, I recommend building using our usual build process. Whether you use the newbuild.sh wrapper script from the fassembler-boot package, or just use fassembler directly, you have a choice of two requirements sets:
- opencore-minimal/tags/0.14.1 is a requirements profile for a fairly stripped down opencore build. It includes supervisord and zeo, but does not include tasktracker, wordpress, or deliverance.
- openplans/releases/opencore-0.14.1-rc builds a more complete stack including tasktracker and wordpress blogs; this is equivalent to what we’d deploy on www.openplans.org. We haven’t fully vetted this build for deployment yet, but it passes all functional and unit tests.
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.
What took so long?
I realize it’s been over a month since Opencore 0.14.0. One thing that added to the time was that, this time I was very careful to create a frozen list of all python packages that opencore depends on, directly or indirectly, so that building this release should be reliable and repeatable. No more depending on whatever happens to currently be in SVN. And since I’d never done this for 0.13 or 0.14.0, it took longer and I ran into more problems than I expect to for future bugfix releases.
Pip was very useful for this job, although I had to massage the output a little bit to make fassembler happy.
I also took the time to edit my notes and document exactly how I make a release. I’m using this as a checklist for now. In the future I’d like to automate some of the more mechanical parts of the process.