fixes and release announcement

Author: Richard Jones

CHANGES.txt

@@ -1,7 +1,7 @@
 This file contains the changes to the Roundup system over time. The entries
 are given with the most recent entry first.
 
-2004-??-?? 0.7.0b2
+2004-03-27 0.7.0b2
 Feature:
 - added CSV export to index pages
 - added emailauditor.py which works around a bug in IE. See
@@ -12,17 +12,19 @@ Feature:
   messages. (sf bug 700265)
 - queries on a per-user basis, and public queries (sf "bug" 891798 :)
 - added DEFAULT_TIMEZONE (sf rfe 895139)
+- added HTML page template to the templating context as "template"
+- added is_retired to HTMLItems in templating
 
 Fixed:
-- Boolean HTML templating was broken
-- Link HTML templating field() was broken
+- Boolean, Date and Link HTML templating was broken
 - fix reporting of test inclusion in postgresql test
 - EditAction was confused about who "self" was
 - edit collision detection was broken for index-page edits
 - sqlite backend wasn't migrating multilink tables correctly
 - use SimpleCookie instead of Cookie (is an alias for the evil SmartCookie)
 - handle older sessions in session dbm
 - make presetunread more resilient to status Class changes
+- HTMLDatabase classes() was broken
 
 
 2004-03-24 0.7.0b1

doc/announcement.txt

@@ -1,5 +1,5 @@
-It is with a huge sigh of relief that I announce this first beta of
-Roundup version 0.7.
+This is the second beta release of Roundup version 0.7. It fixes some bugs
+in the previous beta release and introduces a few new features.
 
 If you're upgrading from an older version of Roundup you *must* follow
 the "Software Upgrade" guidelines given in the maintenance documentation.
@@ -12,22 +12,20 @@ I would *greatly* appreciate people giving this release a whirl with a
 copy of their existing setup. It's only through real-world testing of
 beta releases that we can ensure that older trackers will be OK.
 
-This release introduces far too many features to list here. Some
-highlights:
-
-- added postgresql backend (originally from sf patch 761740, many changes
-  since)
-- RDBMS backends implement their session and one-time-key stores and
-  full-text indexers; thus they are now performing their own locking
-  internally
-- added new "actor" automatic property (indicates user who cause the last
-  "activity")
-- all RDBMS backends have sensible data typed columns and indexes on
-  several columns
-- we support confirming registration by replying to the email (sf bug
-  763668)
-- all HTML templating methods now automatically check for permissions
-  (either view or edit as appropriate), greatly simplifying templates
+Version 0.7 introduces far too many features to list here. I've put
+together a What's New page:
+
+  http://roundup.sourceforge.net/doc-0.7/whatsnew-0.7.html
+
+Some highlights:
+
+- added postgresql backend
+- RDBMS backends have no external locking requirements
+- new "actor" automatic property (user who caused the last "activity")
+- RDBMS backends have data typed columns and indexes on several columns
+- we support confirming registration by replying to the email
+- all HTML templating methods now automatically check for permissions,
+  greatly simplifying templates
 
 Roundup requires python 2.1.3 or later for correct operation.
 

doc/customizing.txt

@@ -2,7 +2,7 @@
 Customising Roundup
 ===================
 
-:Version: $Revision: 1.127 $
+:Version: $Revision: 1.128 $
 
 .. This document borrows from the ZopeBook section on ZPT. The original is at:
    http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx
@@ -1602,6 +1602,7 @@ hasPermission   specific to the "user" class - determine whether the
                 user has a Permission
 is_edit_ok      is the user allowed to Edit the current item?
 is_view_ok      is the user allowed to View the current item?
+is_retired      is the item retired?
 =============== ========================================================
 
 Note that if you have a property of the same name as one of the above

roundup/cgi/templating.py

@@ -1510,7 +1510,6 @@ def __contains__(self, value):
         ''' Support the "in" operator. We have to make sure the passed-in
             value is a string first, not a HTMLProperty.
         '''
-        print (self, value, self._value)
         return str(value) in self._value
 
     def reverse(self):