Hi folks, opencore 0.12.1 was released today.
This is a bugfix release with no user-visible new features.
As with the previous release, it 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.12.1 and then install using python setup.py develop. Or use TOPP’s usual build tools which will do that for you; however, we don’t yet have a requirements profile ready that uses this tag. You could modify requirements/opencore-req.txt if you have an existing fassembler build that you want to upgrade.
The biggest changes in this release are:
- Force project content deletion to be done via POST; if it’s a GET, redirect to a confirmation form. Reduces chance of accidental content delete by non-javascript clients. Thanks to Alex Clark for being so helpful and patient with us on this one.
- Added migrations/unmake-sites.py script to unmake the local sites at the app root and the Plone site root. Run this JUST BEFORE updating to a Plone 3-based version of opencore, which will be the next feature release, version 0.13. Do not run this migration under any other circumstances or you will break your site! For more info, see: https://svn.openplans.org/svn/opencore/trunk/docs/Plone2.5-Plone3-migration.txt
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/07/31, I’m hoping my fellow TOPP employees can provide support while I’m gone.
– Paul Winkler
Get it from https://svn.openplans.org/svn/opencore/tags/0.12.0
I am not uploading a package to Pypi because we still have some work to do before opencore works as an egg. I expect to be working on this over the next few releases. For now, the most reliable way to install is still setup.py develop (or use Fassembler which does it for you).
This is as good a time as any to announce that I hope to release about once a week for the rest of the summer! I will miss a few due to vacations. But hopefully 0.13 will be released by July 21.
What’s new in 0.12.0
This is a summary of user-facing changes. For a complete list, see CHANGES.txt in the source code.
* New form for deleting accounts. This is not linked to from anywhere yet, but if you need to delete a spammer, or if a user wants to leave the site, point your browser at people//delete and fill out the form.
* Zip file export view of project wiki pages. This is not linked to from anywhere yet; you have to visit projects//project-wiki-export.zip. Page attachments are not included.
* Email obfuscation for discussion list views
* fix team AttributeError reported by user on summary page
* fix site_url AttributeError reported by user on password reset
* fix user reported UnboundLocalError on pending page
* possibly resolve user reported error on attachment delete
A decree from the release manager:
Until further notice, we will use the common three-component major.minor.patch version numbering scheme, as popularized by Apache and many other projects.
-
Major releases (e.g. 1.0.0, 2.0.0) indicate major featureset milestones or large backward incompatibilities.
Our major release number will remain 0 until further notice (i.e. until we figure out WTF a 1.0 release would mean).
-
Minor releases (e.g. 0.12.0, 0.13.0) indicate new features.
Minor releases may also require data migrations and will generally also include all the bugfixes since the previous minor release.
-
Patch (aka “point” or “micro”) releases (e.g. 0.12.1, 0.12.2) may only contain bugfixes, and must be 100% backward compatible.
No new features are allowed in a patch release. No data migrations may be required by a patch release except as strictly required for a critical bugfix, in which case I might decide to bump the minor version anyway.
You might notice with this policy that minor numbers will get bumped quite often. That’s okay. There’s nothing wrong with numbering a release eg. 0.87.0, except that it would strongly suggest a need to re-evaluate the 1.0 milestone 
This is basically the same numbering scheme that we’ve had since we broke out of the infinite 0.9.7.x loop. The main difference is organizational - one person (me) will be paying attention to keeping it consistent. That was the only real problem with Ethan’s previous plan.
