Well, here it is over a month late; sorry for the delay, but real life reared its fascinating head: My baby girl was born early, on January 23, the day I had planned to release opencore 0.16. I am sorry to all the WSF people who had hoped to have an upgrade to install before the Belem conference. I hear it was a great meeting.
Should I upgrade?
This release consists almost entirely of bug fixes. It should be a safe. minor upgrade from 0.15. I almost wish I’d called it 0.15.1, but it’s too late to change my mind 
What’s New Since 0.15
Data Migrations:
Nothing new this time. If you’re upgrading from a release older than 0.15, you should check for older migrations that need running; see CHANGES.txt in the source code or previous release announcements on this blog.
Features:
Nothing you’d notice really :-) A slight enhancement was added to give the proper project context based on Deliverance headers; if you don’t know what that means, you probably don’t care.
Also, some minor speed enhancements.
Bug fixes:
* Fixed a bug in utility.email_sender that prevented keyword args from being used in translation interpolation as expected (slinkp)
* Fixed invite reminder email so the message gets correctly translated including the passed variables (slinkp)
* Fixed unicode decode error in member contact form (and hopefully avoid related errors on other pages). (#2768) (slinkp)
* RSS feeds of wiki page history was prohibitively expensive. Fixed. (#2766) (slinkp)
* The user folder ID migration fix from opencore 0.14 (see below) would barf on a few mysterious users. We work around that now, although the real fix is to upgrade membrane, which is done in the latest Products bundle. (slinkp)
* The member area title migration was tweaked to avoid some unnecessary data changes, and commit every so often to avoid conflict errors. (slinkp)
* The workflow update migration was refactored to commit every so often, to avoid conflict errors. (slinkp)
* Project summary now correctly shows the blank slate version of the BlogSummaryViewlet when there are no blog posts. (slinkp, jhammel)
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.16.0 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/branches/opencore-0.16 builds a more complete stack based on the 0.16 branch, including tasktracker and wordpress blogs. We are in process of vetting this for deployment to www.openplans.org (this site). Once that’s done, we’ll put a tag of these requirements in openplans/releases.
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.