@@ -110,6 +110,15 @@ highly recommended, as the effort is minimal.
1101104. You might also wish to remove the redundant query editing section from the
111111 ``user.item.html`` page.
112112
113+ ZRoundup reinstated
114+ -------------------
115+
116+ The Zope interface, ZRoundup, lives again!
117+
118+ See the `upgrading documentation`__ if you wish to use it.
119+
120+ __ upgrading.html#zroundup-changes
121+
113122
114123Simple support for collision detection
115124--------------------------------------
@@ -185,6 +194,11 @@ have permission to view the information.
185194This removes the need for the template to perform those checks, which was
186195just plain messy.
187196
197+ Some new permissions will need to be created in your trackers to cope with
198+ this change, as outlined in the `upgrading documentation`__.
199+
200+ __ upgrading.html#permission-assignments
201+
188202
189203Standards changes
190204-----------------
@@ -270,20 +284,26 @@ Postgresql is a good choice if you expect your tracker to grow very large,
270284and are expecting many users.
271285
272286
273- Other improvements
274- ------------------
287+ API change
288+ ----------
289+
290+ The Database.curuserid attribute was removed. Any code referencing this
291+ attribute should be replaced with a call to Database.getuid().
275292
276- All RDBMS backends now have indexes automatically created on critical
277- table columns.
278293
279- Additionally, the RDBMS backends also implement their own session,
280- one-time-key and full-text indexing stores. These were previously external
281- dbm stores. This change allows control of locking the database to be
282- completely handed over to the RDBMS.
294+ New configuration options
295+ -------------------------
283296
284- Date values capture fractions of seconds now. Note that the MySQL backend
285- is not capable of storing this precision though, so it will be lost for
286- users of that backend.
297+ - Added DEFAULT_TIMEZONE which allows the tracker to have a different
298+ default to UTC when users don't specify their own preference.
299+
300+ - Added EMAIL_CHARSET (in 0.6.6, but worth mentioning here) which hard-codes
301+ the character set to be used when sending email from Roundup. This works
302+ around some email clients' inability to cope well with UTF-8 (the
303+ default).
304+
305+ - ERROR_MESSAGES_TO and DISPATCHER_EMAIL as described above in `Dispatcher
306+ configuration`_.
287307
288308
289309Typed columns in RDBMS backends
@@ -380,4 +400,21 @@ to another. Example usage::
380400which copies users 3, 4, 5, 6, 7, 8, 9, 10, 14 and 16.
381401
382402
403+ Other improvements
404+ ------------------
405+
406+ - All RDBMS backends now have indexes automatically created on critical
407+ table columns.
408+
409+ - Additionally, the RDBMS backends also implement their own session,
410+ one-time-key and full-text indexing stores. These were previously external
411+ dbm stores. This change allows control of locking the database to be
412+ completely handed over to the RDBMS.
413+
414+ - Date values capture fractions of seconds now. Note that the MySQL backend
415+ is not capable of storing this precision though, so it will be lost for
416+ users of that backend.
417+
418+
419+
383420.. _`customisation documentation`: customizing.html
0 commit comments