Finished implementation of session and one-time-key stores for RDBMS

[roundup.git] / CHANGES.txt

diff --git a/CHANGES.txt b/CHANGES.txt
index 2cc96571d6e8ec08f668d3f32003b2b7a19d694c..f0c79f6082e056cdfb7035a830f73f03ceabb0d3 100644 (file)
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,6 +3,8 @@ are given with the most recent entry first.
 
 200?-??-?? 0.7.0
 Feature:
+- added new "actor" automatic property (indicates user who cause the last
+  "activity"
 - simple support for collision detection (sf rfe 648763)
 - support confirming registration by replying to the email (sf bug 763668)
 - support setgid and running on port < 1024 (sf patch 777528)
@@ -11,11 +13,9 @@ Feature:
 - added postgresql backend (originally from sf patch 761740, many changes
   since)
 - all RDBMS backends now have indexes on several columns
+- RDBMS backends implement their session and one-time-key stores
 - change nosymessage and send_message to accept msgid=None (RFE #707235).
 - handle Resent-From: headers (sf bug 841151)
-- existing trackers (ie. live ones) may be used as templates for new
-  trackers - the TEMPLATE-INFO.txt name entry has the tracker's dir name
-  appended (so the demo tracker's template name is "classic-demo")
 - always sort MultilinkHTMLProperty in the correct order, usually
   alphabetically (sf feature 790512).
 - added script for copying user(s) from tracker to tracker (sf patch
@@ -74,12 +74,23 @@ Cleanup:
   * form_parser.py - parsePropsFromForm & extractFormList in a FormParser class
 
 
-2004-??-?? 0.6.7
+2004-??-?? 0.6.8
+Fixed:
+- existing trackers (ie. live ones) may be used as templates for new
+  trackers - the TEMPLATE-INFO.txt name entry has the tracker's dir name
+  appended (so the demo tracker's template name is "classic-demo")
+
+
+2004-03-01 0.6.7
 Fixed:
+- be more backward-compatible when asking for EMAIL_CHARSET
 - made error on create consistent with edit when user enters invalid data
   for Multilink and Link form fields (sf bug 904072)
 - made errors from bad input in the quick "Show issue:" form more
   user-friendly (sf bug 904064)
+- don't add a query to a user's list if it's already there
+- nicer invalid property error in HTML templating
+- use EMAIL_CHARSET for message body too (still sf bug 900046)
 
 
 2004-02-25 0.6.6