From: schlatterbeck Date: Fri, 13 May 2011 07:56:45 +0000 (+0000) Subject: release preparation X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=e60064f0d789db473b1f51d58e7f7e0aa83c70a4;p=roundup.git release preparation git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/roundup/trunk@4603 57a73879-2fb5-44c3-a270-3262357dd7e2 --- diff --git a/CHANGES.txt b/CHANGES.txt index c5ea367..6f36bf9 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -2,7 +2,7 @@ This file contains the changes to the Roundup system over time. The entries are given with the most recent entry first. If no other name is given, Richard Jones did the change. -20XX-XX-XX 1.4.17 (rXXXX) +2011-05-13 1.4.17 (r4603) Features: diff --git a/doc/announcement.txt b/doc/announcement.txt index 14e7529..52881f6 100644 --- a/doc/announcement.txt +++ b/doc/announcement.txt @@ -1,52 +1,107 @@ -I'm proud to release version 1.4.16 of Roundup which introduces some +I'm proud to release version 1.4.17 of Roundup which introduces some minor features and, as usual, fixes some bugs: Features: -- allow trackers to override the classes used to render properties in - templating per issue2550659 (thanks Ezio Melotti) -- new mailgw configuration item "subject_updates_title": If set to "no" - a changed subject in a reply to an issue will not update the issue - title with the changed subject. Thanks to Arkadiusz Kita and Peter - Funk for requesting the feature and discussing the implementation. - http://thread.gmane.org/gmane.comp.bug-tracking.roundup.user/10169 -- new rdbms config item sqlite_timeout makes the previously hard-coded - timeout of 30 seconds configurable. This is the time a client waits - for the locked database to become free before giving up. Used only for - SQLite backend. -- new mailgw config item unpack_rfc822 that unpacks message attachments - of type message/rfc822 and attaches the individual parts instead of - attaching the whole message/rfc822 attachment to the roundup issue. +- Allow declaration of default_values for properties in schema. +- Add explicit "Search" permissions, see Security Fix below. +- Add "lookup" method to xmlrpc interface (Ralf Schlatterbeck) +- Multilinks can be filtered by combining elements with AND, OR and NOT + operators now. A javascript gui was added for "keywords", see issue2550648. + Developed by Sascha Teichmann; funded by Intevation. (Bernhard Reiter) +- Factor MailGW message parsing into a separate class, thanks to John + Kristensen who did the major work in issue2550576 -- I wouldn't + have attempted it without this. Fixes issue2550576. (Ralf) +- Now if the -C option to roundup-mailgw specifies "issue" this refers + to an issue-like class. The real class is determined from the + configured default class, or the -c option to the mailgw, or the class + resulting from mail subject parsing. We also accept multiple -S + options for the same class now. (Ralf) +- Optimisation: Late evaluation of Multilinks (only in rdbms backends): + previously we materialized each multilink in a Node -- this creates an + SQL query for each multilink (e.g. 'files' and 'messages' for each + line in the issue index display) -- even if the multilinks aren't + displayed. Now we compute multilinks only if they're accessed (and + keep them cached). +- Add a filter_iter similar to the existing filter call. This feature is + considered experimental. This is currently not used in the + web-interface but passes all tests for the filter call except sorting + by Multilinks (which isn't supported by SQL and isn't a sane concept + anyway). When using filter_iter instead of filter this saves a *lot* + of SQL queries: Filter returns only the IDs of Nodes in the database, + the additional content of a Node has to be fetched in a separate SQL + call. The new filter_iter also returns the IDs of Nodes (one by one, + it's an iterator) but pre-seeds the cache with the content of the + Node. The information needed for seeding the cache is retrieved in the + same SQL query as the ids. Fixed: -- fixed reporting of source missing warnings -- relevant tests made locale independent, issue2550660 (thanks - Benni Baermann for reporting). -- fix for incorrect except: syntax, issue2550661 (thanks Jakub Wilk) -- No longer use the root logger, use a logger with prefix "roundup", - see http://thread.gmane.org/gmane.comp.bug-tracking.roundup.devel/5356 -- improve handling of '>' when URLs are converted to links, issue2550664 - (thanks Ezio Melotti) -- fixed registration, issue2550665 (thanks Timo Paulssen) -- make sorting of multilinks in the web interface more robust, issue2550663 -- Fix charset of first text-part of outgoing multipart messages, thanks Dirk - Geschke for reporting, see - http://thread.gmane.org/gmane.comp.bug-tracking.roundup.user/10223 -- Fix handling of incoming message/rfc822 attachments. These resulted in - a weird mail usage error because the email module threw a TypeError - which roundup interprets as a Reject exception. Fixes issue2550667. - Added regression tests for message/rfc822 attachments with and without - configured unpacking (mailgw unpack_rfc822, see Features above) - Thanks to Benni Baermann for reporting. -- Allow search_popup macro to work with all db classes, issue2550567 - (thanks John Kristensen) -- lower memory footprint for (journal-) import +- Security Fix: Add a check for search-permissions: now we allow + searching for properties only if the property is readable without a + check method or if an explicit search permission (see above unter + "Features) is given for the property. This fixes cases where a user + doesn't have access to a property but can deduce the content by + crafting a clever search, group or sort query. + see doc/upgrading.txt for how to fix your trackers! (Ralf Schlatterbeck). +- Range support in roundup-server so large files can be served, + e.g. media files on iOS/iPads; issue2550694. (Bernhard Reiter; + Thanks to Jon C. Thomason for the patch.) +- Fix search for xapian 1.2 issue2550676 + (Bernhard Reiter; Thanks to Olly Betts for providing the patch.) +- Some minor typos fixed in doc/customizing.txt (Thanks Ralf Hemmecke). +- XML-RPC documentation now linked from the docs/index (Bernhard Reiter). +- Fix setting of sys.path when importing schema.py, fixes issue2550675, + thanks to Bryce L Nordgren for reporting. (Ralf Schlatterbeck) +- clear the cache on commit for rdbms backends: Don't carry over cached + values from one transaction to the next (there may be other changes + from other transactions) see new ConcurrentDBTest for a + read-modify-update cycle that fails with the old caching behavior. + (Ralf Schlatterbeck) +- Fix incorrect setting of template in customizing.txt example action, + patch via issue2550682 (thanks John Kristensen) +- Configuration issue: On some postgresql 8.4 installations (notably on + debian squeeze) the default template database used for database + creation doesn't match the needed character encoding UTF8 -- a new + config option 'template' in the rdbms section now allows specification + of the template. You know you need this option if you get the error + message: + psycopg2.DataError: new encoding (UTF8) is incompatible with the + encoding of the template database (SQL_ASCII) + HINT: Use the same encoding as in the template database, or use + template0 as template. + (Ralf Schlatterbeck) +- Fixed bug in mailgw refactoring, patch issue2550697 (thanks Hubert + Touvet) +- Fix Password handling security issue2550688 (thanks Joseph Myers for + reporting and Eli Collins for fixing) -- this fixes all observations + by Joseph Myers except for auto-migration of existing passwords. +- Add new config-option 'migrate_passwords' in section 'web' to + auto-migrate passwords at web-login time. Default for the new option + is "yes" so if you don't want that passwords are auto-migrated to a + more secure password scheme on user login, set this to "no" before + running your tracker(s) after the upgrade. +- Add new config-option 'password_pbkdf2_default_rounds' in 'main' + section to configure the default parameter for new password + generation. Set this to a higher value on faster systems which want + more security. Thanks to Eli Collins for implementing this (see + issue2550688). +- Fix documentation for roundup-server about the 'host' parameter as + suggested in issue2550693, fixes the first part of this issue. Make + 'localhost' the new default for this parameter, note the upgrading + documentation of changed behaviour. We also deprecate the empty host + parameter for binding to all interfaces now (still left in for + compatibility). Thanks to Toni Mueller for providing the first version + of this patch and discussing implementations. +- Fixed bug in filter_iter refactoring (lazy multilinks), in rare cases + this would result in duplicate multilinks to the same node. We're now + going the safe route and doing lazy evaluation only for read-only + access, whenever updates are done we fetch everything. If you're upgrading from an older version of Roundup you *must* follow the "Software Upgrade" guidelines given in the maintenance documentation. -Roundup requires python 2.3 or later (but not 3+) for correct operation. +Roundup requires python 2.4 or later (but not 3+) for correct operation. To give Roundup a try, just download (see below), unpack and run:: @@ -80,7 +135,7 @@ Roundup manages a number of issues (with flexible properties such as The system will facilitate communication among the participants by managing discussions and notifying interested parties when issues are edited. One of the major design goals for Roundup that it be simple to get going. Roundup -is therefore usable "out of the box" with any python 2.3+ (but not 3+) +is therefore usable "out of the box" with any python 2.4+ (but not 3+) installation. It doesn't even need to be "installed" to be operational, though an install script is provided. diff --git a/roundup/__init__.py b/roundup/__init__.py index d4e4536..d53a610 100644 --- a/roundup/__init__.py +++ b/roundup/__init__.py @@ -68,6 +68,6 @@ much prettier cake :) ''' __docformat__ = 'restructuredtext' -__version__ = '1.4.16' +__version__ = '1.4.17' # vim: set filetype=python ts=4 sw=4 et si