Poi 1.1
Up to Product page
For additional information about this project, please visit the
project page.
Available downloads
Release Notes
| Tested with | Plone 3.0, Plone 2.5 |
|---|---|
| State | Final release |
| License | GPL |
| Release Manager | Maurits van Rees |
| Released | 2007/12/28 |
Highlights of this release include:
This release introduces Plone 3.0 compatibility while keeping compatibility with Plone 2.5. [Alexander Limi and Maurits van Rees]
Link detection. Trackers now have an svnUrl field. For example, if your product is hosted in the Plone collective you can set this field to http://dev.plone.org/collective/changeset/%(rev)s. Then you can type 'r42' in an issue/response (any intelligenttext field) and get a link to that changeset. [Daniel Nouri]
Advanced issue search form now has a way to search for issues that match all tags, not only any, which helps when you're working a lot with tags. [Daniel Nouri]
Added a log-view for Poi trackers. This view renders a report on the most recent additions to the tracker; as such it will be similar to what is sent out as e-mail notifications. [Malthe Borch]
Cleanup of translations. [Maurits van Rees]
Fix i18n of email sending (think accented characters) [Maurits van Rees, Stefano Deponti]
Loads of small bug fixes. [Maurits van Rees and others]
Fix Inconsistent linking to other issues and changesets:
- Links in the steps field of an issue are now also detected.
- Allow more links to be detected:
- issues: #1, issue:1, ticket:1, bug:1.
- changesets/revisions: r1, changeset:1, [1].
- Add lots of tests for the link detection in a tracker.
[Per Erik Strandberg, maurits]
Fix "TypeError: can't pickle code objects" when updating the schema of PoiTrackers. Done by moving the 'atLeastOne' validator from content/PoiTracker.py to validators.py and registering it (and rename it to isDataGridFilled). Fixes http://plone.org/products/poi/issues/160 [maurits]
Dependencies:
- Plone: 2.5+ on Zope 2.9 OR 3.0+ on Zope 2.10
- DataGridField
- AddRemoveWidget
- intelligenttext (but this is installed by default in Plone 3) Note: when going from Plone 2.5 to 3.0, please first uninstall intelligenttext, then create a new instance with Plone 3. Then run the portal_migration, which will install the new plone.intelligenttext library for you.
- For migration from versions before 1.0b2, contentmigration is required.
- For PloneSoftwareCenter integration, PloneSoftwareCenter is required. See http://plone.org/products/plonesoftwarecenter Tested on Plone 2.5 with: PloneSoftwareCenter-1.0-RC.tgz Tested on Plone 3.0 with: PloneSoftwareCenter-1.5-alpha1.tar.gz
Change log