summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: ca1a13b)
raw | patch | inline | side by side (parent: ca1a13b)
author | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
Wed, 17 Sep 2003 22:30:30 +0000 (22:30 +0000) | ||
committer | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
Wed, 17 Sep 2003 22:30:30 +0000 (22:30 +0000) |
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@1880 57a73879-2fb5-44c3-a270-3262357dd7e2
CHANGES.txt | patch | blob | history | |
doc/upgrading.txt | patch | blob | history |
diff --git a/CHANGES.txt b/CHANGES.txt
index 4e7f1b2a78d98efdc91e12a006c255a1bdbb9097..bad5409621c89a0c2c69d43786da0dbef3b14cd6 100644 (file)
--- a/CHANGES.txt
+++ b/CHANGES.txt
Feature:
- support confirming registration by replying to the email (sf bug 763668)
+
2003-09-?? 0.6.2
Fixed:
- cleaned up, clarified internal caching API in *dbm backends
- stopped pyc writing to current directory! yay! (patch 800718 with changes)
- fixed file leak in detector initialisation (patch 800715)
- commented out example tracker homes (patch 800720)
+- added note about hidden :template var in user.item (bug 799842)
2003-08-31 0.6.1
diff --git a/doc/upgrading.txt b/doc/upgrading.txt
index e77d41d46837c206b2af33dd916e9803ef944c70..cf69f1b118f64980874fe039325ebc24b003f5a3 100644 (file)
--- a/doc/upgrading.txt
+++ b/doc/upgrading.txt
be replaced with a call to Database.getuid().
+
Migrating from 0.5 to 0.6
=========================
+
0.6.0 Configuration
-------------------
<tracker home>/detectors/__init__.py. Don't worry, the "classic" __init__ is a
one-size-fits-all, so it'll work even if you've added/removed detectors.
+0.6.0 Templating changes
+------------------------
+
+The ``user.item`` template (in the tracker home "templates" directory)
+needs to have the following hidden variable added to its form (between the
+``<form...>`` and ``</form>`` tags::
+
+ <input type="hidden" name=":template" value="item">
+
0.6.0 Form handling changes
---------------------------
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
---------------------------
and mail interfaces in local time. It will also accept any Date info in
local time, convert and store it in GMT.
+
0.6.0 Search page structure
---------------------------