--- a/doc/upgrading.txt	Fri Jan 24 06:22:03 2003 +0000
+++ b/doc/upgrading.txt	Mon Jan 27 16:32:50 2003 +0000
@@ -46,6 +46,40 @@
   is no tool for converting such data, the only solution is to close
   appropriate old issues and create new ones with the same content.
 
+0.6.0 User' timezone support
+----------------------------
+
+- From version 0.6.0 roundup supports displaying of Date data in user' local
+  timezone if he/she has provided timezone information. To make it possible
+  some modification to tracker's schema and HTML templates are required.
+  First you should add string property 'timezone' to user class in dbinit.py
+  like this:
+  
+    user = Class(db, "user", 
+                    username=String(),   password=Password(),
+                    address=String(),    realname=String(), 
+                    phone=String(),      organisation=String(),
+                    alternate_addresses=String(),
+                    queries=Multilink('query'), roles=String(),
+                    timezone=String())
+  
+  And second - html interface. Add following lines to
+  $TRACKER_HOME/html/user.item template:
+  
+	 <tr>
+	  <th>Timezone</th>
+	  <td tal:content="structure context/timezone/field">timezone</td>
+	 </tr>
+
+  After that all users should be able to provide their timezone information.
+  Timezone should be a positive or negative integer - offset from GMT.
+
+  After providing timezone, roundup will show all dates values, found in web
+  and mail interfaces in local time. It will also accept any Date info in
+  local time, convert and store it in GMT.
+
+  However you are not forced to make these modifications. By default roundup
+  will assume timezone=0 and will work as previous versions did.
 
 Migrating from 0.4.x to 0.5.0
 =============================