--- a/BUILD.txt	Fri Mar 03 02:19:27 2006 +0000
+++ b/BUILD.txt	Fri Mar 03 02:29:10 2006 +0000
@@ -6,7 +6,7 @@
 source release. Users of Roundup should read the doc/installation.txt file
 to find out how to install this software.
 
-Building a release of Roundup is done by running:
+Building and distributing a release of Roundup is done by running:
 
 1.  Make sure the unit tests run! "./run_tests.py"
 2.  Tag the CVS for the release, eg. "cvs tag -R release-0-6-3"
@@ -29,6 +29,11 @@
 11. Generate gpg signature with "gpg -a --detach-sign"
 12. python setup.py bdist_rpm
 13. python setup.py bdist_wininst
+14. Send doc/announcement.txt to python-announce@python.org
+15. Notify any other news services as appropriate...
+
+      http://freshmeat.net/projects/roundup/
+
 
 So, those commands in a nice, cut'n'pasteable form::
 
@@ -40,26 +45,7 @@
  python setup.py sdist --quiet
  python setup.py bdist_rpm
  python setup.py bdist_wininst
- python2.3 setup.py register
-
+ python setup.py register
+ python2.5 setup.py sdist upload --sign
 
 
-Distributing Releases
-=====================
-
-Once a release is built, follow these steps:
-
-1. FTP the tar.gz from the dist directory to to the "incoming" directory on
-   "upload.sourceforge.net".
-2. Make a quick release at:
-    http://sourceforge.net/project/admin/qrs.php?package_id=&group_id=31577
-3. PyPI registration / upload::
-
-     python setup.py register
-     python2.5 setup.py sdist upload --sign
-
-4. Send doc/announcement.txt to python-announce@python.org
-5. Notify any other news services as appropriate...
-
-   http://freshmeat.net/projects/roundup/
-

--- a/CHANGES.txt	Fri Mar 03 02:19:27 2006 +0000
+++ b/CHANGES.txt	Fri Mar 03 02:29:10 2006 +0000
@@ -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.
 
-2006-??-?? 1.1.1
+2006-03-03 1.1.1
 Fixed:
 - failure with browsers not sending "Accept-Language" header
   (sf bugs 1429646 and 1435335)

--- a/doc/announcement.txt	Fri Mar 03 02:19:27 2006 +0000
+++ b/doc/announcement.txt	Fri Mar 03 02:29:10 2006 +0000
@@ -1,23 +1,28 @@
-I'm proud to release this, the 1.1.0 release of Roundup.
-
-Feature:
-
-- trackers may configure custom stop-words for the full-text indexer
-- login may now be for a single session (and this is the default)
-- trackers may hide exceptions from web users (they will be mailed to the
-  tracker admin) (hiding is the default)
-- include "clear this message" link in the "ok" message bar
+I'm proud to release this, the 1.1.1 release of Roundup.
 
 Fixed:
 
-- fixes in scripts/import_sf.py
-- fix some unicode bugs in roundup-admin import
-- Xapian indexer wasn't actually being used and its reindexing of existing
-  data was busted to boot
-- roundup-admin import wasn't indexing message content
-- allow dispname to be passed to renderWith (sf bug 1424587)
-- rename dispname to @dispname to avoid name clashes in the future
-- fixed schema migration problem when Class keys were removed
+- failure with browsers not sending "Accept-Language" header
+  (sf bugs 1429646 and 1435335)
+- translate class name in "required property not supplied" error message
+  (sf bug 1429669)
+- error in link property lookups with numeric-alike key values (sf bug 1424550)
+- ignore UTF-8 BOM in .po files
+- add permission filter to menu() implementations (sf bug 1431188)
+- lithuanian translation updated by Nerijus Baliunas (sf patch 1411175)
+- incompatibility with python2.3 in the mailer module (sf bug 1432602)
+- typo in SMTP TLS option name: "MAIL_TLS_CERFILE" (sf bug 1435452)
+- email obfuscation code in html templating is more robust
+- blank-title subject line handling (sf bug 1442121)
+- "All users may only view and edit issues, files and messages they
+  create" example in docs (sf bug 1439086)
+- saving of queries (sf bug 1436169)
+- "Adding a new constrained field to the classic schema" example in docs
+  (sf bug 1433118)
+- security check in mailgw (sf bug 1442145)
+- "clear this message" (sf bug 1429367)
+- escape all uses of "schema" in mysql backend (sf bug 1397569)
+- date spec wasn't allowing week intervals
 
 If you're upgrading from an older version of Roundup you *must* follow
 the "Software Upgrade" guidelines given in the maintenance documentation.

--- a/doc/upgrading.txt	Fri Mar 03 02:19:27 2006 +0000
+++ b/doc/upgrading.txt	Fri Mar 03 02:29:10 2006 +0000
@@ -13,6 +13,36 @@
 
 .. contents::
 
+Migrating from 1.1.0 to 1.1.1
+=============================
+
+1.1.1 "Clear this message"
+--------------------------
+
+In 1.1.1, the standard ``page.html`` template includes a "clear this message"
+link in the green "ok" message bar that appears after a successful edit
+(or other) action.
+
+To include this in your tracker, change the following in your ``page.html``
+template::
+
+ <p tal:condition="options/ok_message | nothing" class="ok-message"
+    tal:repeat="m options/ok_message" tal:content="structure m">error</p>
+
+to be::
+
+ <p tal:condition="options/ok_message | nothing" class="ok-message">
+   <span tal:repeat="m options/ok_message"
+      tal:content="structure string:$m <br/ > " />
+    <a class="form-small" tal:attributes="href request/current_url"
+       i18n:translate="">clear this message</a>
+ </p>
+
+
+If you implemented the "clear this message" in your 1.1.0 tracker, then you
+should change it to the above and it will work much better!
+
+
 Migrating from 1.0.x to 1.1.0
 =============================
 

--- a/roundup/__init__.py	Fri Mar 03 02:19:27 2006 +0000
+++ b/roundup/__init__.py	Fri Mar 03 02:29:10 2006 +0000
@@ -15,7 +15,7 @@
 # BASIS, AND THERE IS NO OBLIGATION WHATSOEVER TO PROVIDE MAINTENANCE,
 # SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
 # 
-# $Id: __init__.py,v 1.36 2006-02-08 04:46:41 richard Exp $
+# $Id: __init__.py,v 1.37 2006-03-03 02:29:10 richard Exp $
 
 '''Roundup - issue tracking for knowledge workers.
 
@@ -68,6 +68,6 @@
 '''
 __docformat__ = 'restructuredtext'
 
-__version__ = '1.1.0'
+__version__ = '1.1.1'
 
 # vim: set filetype=python ts=4 sw=4 et si

--- a/setup.py	Fri Mar 03 02:19:27 2006 +0000
+++ b/setup.py	Fri Mar 03 02:29:10 2006 +0000
@@ -16,7 +16,7 @@
 # BASIS, AND THERE IS NO OBLIGATION WHATSOEVER TO PROVIDE MAINTENANCE,
 # SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
 #
-# $Id: setup.py,v 1.88 2006-02-10 00:16:12 richard Exp $
+# $Id: setup.py,v 1.89 2006-03-03 02:29:09 richard Exp $
 
 from distutils.core import setup, Extension
 from distutils.util import get_platform
@@ -351,24 +351,29 @@
 If you're upgrading from an older version of Roundup you *must* follow
 the "Software Upgrade" guidelines given in the maintenance documentation.
 
-Feature:
-
-- trackers may configure custom stop-words for the full-text indexer
-- login may now be for a single session (and this is the default)
-- trackers may hide exceptions from web users (they will be mailed to the
-  tracker admin) (hiding is the default)
-- include "clear this message" link in the "ok" message bar
-
 Fixed:
 
-- fixes in scripts/import_sf.py
-- fix some unicode bugs in roundup-admin import
-- Xapian indexer wasn't actually being used and its reindexing of existing
-  data was busted to boot
-- roundup-admin import wasn't indexing message content
-- allow dispname to be passed to renderWith (sf bug 1424587)
-- rename dispname to @dispname to avoid name clashes in the future
-- fixed schema migration problem when Class keys were removed
+- failure with browsers not sending "Accept-Language" header
+  (sf bugs 1429646 and 1435335)
+- translate class name in "required property not supplied" error message
+  (sf bug 1429669)
+- error in link property lookups with numeric-alike key values (sf bug 1424550)
+- ignore UTF-8 BOM in .po files
+- add permission filter to menu() implementations (sf bug 1431188)
+- lithuanian translation updated by Nerijus Baliunas (sf patch 1411175)
+- incompatibility with python2.3 in the mailer module (sf bug 1432602)
+- typo in SMTP TLS option name: "MAIL_TLS_CERFILE" (sf bug 1435452)
+- email obfuscation code in html templating is more robust
+- blank-title subject line handling (sf bug 1442121)
+- "All users may only view and edit issues, files and messages they
+  create" example in docs (sf bug 1439086)
+- saving of queries (sf bug 1436169)
+- "Adding a new constrained field to the classic schema" example in docs
+  (sf bug 1433118)
+- security check in mailgw (sf bug 1442145)
+- "clear this message" (sf bug 1429367)
+- escape all uses of "schema" in mysql backend (sf bug 1397569)
+- date spec wasn't allowing week intervals
 ''',
         'author': "Richard Jones",
         'author_email': "richard@users.sourceforge.net",