--- a/doc/upgrading.txt	Fri Mar 26 05:16:03 2004 +0000
+++ b/doc/upgrading.txt	Fri Mar 26 06:02:20 2004 +0000
@@ -12,116 +12,6 @@
 Migrating from 0.6 to 0.7
 =========================
 
-0.7.0 Saving and sharing of user queries
-----------------------------------------
-
-Due to popular demand, the user query saving mechanisms have been
-overhauled. This means that queries remember the user that created them
-and they may be marked as being private for a particular user.
-
-You *are not required* to make these changes. You only need to make them
-if you wish to use the new query editing features. It's highly
-recommended, as the effort is minimal.
-
-1. You will need to edit your tracker's ``dbinit.py`` to change the way
-   queries are stored. Change the lines::
-
-      query = Class(db, "query",
-                      klass=String(),     name=String(),
-                      url=String())
-      query.setkey("name")
-
-   to::
-
-      query = Class(db, "query",
-                      klass=String(),     name=String(),
-                      url=String(),       private_for=Link('user'))
-
-   That is, add the "private_for" property, and remove the line that says
-   ``query.setkey("name")``. The latter is the most important edit here.
-
-2. You will also need to copy the ``query.edit.html`` template page from the
-   ``templates/classic/html/`` directory of the source to your tracker's
-   ``html`` directory.
-
-3. Once you've done that, edit the tracker's ``page.html`` template to
-   change::
-
-    <td rowspan="2" valign="top" class="sidebar">
-     <p class="classblock" tal:condition="request/user/queries">
-      <b>Your Queries</b><br>
-      <tal:block tal:repeat="qs request/user/queries">
-
-   to::
-
-    <td rowspan="2" valign="top" class="sidebar">
-     <p class="classblock">
-      <b>Your Queries</b> (<a href="query?@template=edit">edit</a>)<br>
-      <tal:block tal:repeat="qs request/user/queries">
-
-   That is, you're removing the ``tal:condition`` and adding a link to the
-   new edit page.
-
-4. You might also wish to remove the redundant query editing section from the
-   ``user.item.html`` page.
-
-
-0.7.0 Added Dispatcher role
----------------------------
-
-A new config option has been added that specifies the email address of
-a "dispatcher" role.  This email address acts as a central sentinel for
-issues coming into the system. You can configure it so that all e-mail
-error messages get bounced to them, them and the user in question, or
-just the user (default).
-
-To toggle these switches, add the "DISPATCHER_EMAIL" and
-"ERROR_MESSAGES_TO" configuration values to your tracker's ``config.py``.
-See the `customisation documentation`_ for how to use them.
-
-
-0.7.0 Added CSV export action
------------------------------
-
-A new action has been added which exports the current index page or search
-result as a comma-separated-value (CSV) file.
-
-To use it, add this to your "index" templates:
-
-<a tal:attributes="href python:request.indexargs_url('issue',
-            {'@action':'csv_export'})">Download as CSV</a>
-
-Making sure that the ``'issue'`` part matches the class name of the page
-you're editing.
-
-
-0.7.0 Typed columns in MySQL backend
-------------------------------------
-
-The MySQL (and Postgresql for that matter) backend now creates tables with
-appropriate column datatypes (not just varchar).
-
-Your database will be automatically migrated to use the new schemas, but
-it will take time. It's probably a good idea to make sure you do this as
-part of the upgrade when users are not expected to be using the system.
-
-
-0.7.0 Permission setup
-----------------------
-
-0.7 automatically sets up the Edit and View Permissions for all classes,
-thus you don't need to do so. Feel free to remove the code::
-
-    # Add new Permissions for this schema
-    for cl in 'issue', 'file', 'msg', 'user', 'query', 'keyword':
-        db.security.addPermission(name="Edit", klass=cl,
-            description="User is allowed to edit "+cl)
-        db.security.addPermission(name="View", klass=cl,
-            description="User is allowed to access "+cl)
-
-from your ``dbinit.py``.
-
-
 0.7.0 Permission assignments
 ----------------------------
 
@@ -147,30 +37,6 @@
         db.security.addPermissionToRole('User', p)
 
 
-0.7.0 New "actor" property
---------------------------
-
-Roundup's database has a new per-item property "actor" which reflects the
-user performing the last "actvitiy". See the classic template for ways to
-integrate this new property into your interface.
-
-The property will be automatically added to your existing database.
-
-
-0.7.0 Extending the cgi interface
----------------------------------
-
-Before 0.7.0 adding or extending web actions was done by overriding or adding
-methods on the Client class. Though this approach still works to provide
-backwards compatibility, it is recommended you upgrade to the new approach, as
-described in the `Defining new web actions`__ section of the customization
-documentation. You might also want to take a look at the `Using an external
-password validation source`__ example.
-
-__ customizing.html#defining-new-web-actions
-__ customizing.html#using-an-external-password-validation-source
-
-
 0.7.0 Getting the current user id
 ---------------------------------
 
@@ -178,14 +44,6 @@
 should be replaced with a call to Database.getuid().
 
 
-0.7.0 Email character set
--------------------------
-
-The default character set for sending email is UTF-8 (ie. Unicode). If you
-have users whose email clients can't handle UTF-8 (eg. Eudora) then you
-will need to edit the new config.py variable ``EMAIL_CHARSET``.
-
-
 0.7.0 ZRoundup changes
 ----------------------