Set min python version for release 1.6. Login changes now required,

fix incorrect file name, add filename for keyword entry improvement.

Author: rouilj

doc/upgrading.txt

@@ -11,9 +11,10 @@ then you don't need to do anything. If you're upgrading from 0.5.6 to
 0.6.8 though, you'll need to check the "0.5 to 0.6" and "0.6.x to 0.6.3"
 steps.
 
-**IMPORTANT** The v1.5.x releases of Roundup will be the last to support Python
-v2.5. Support for Python v2.5 will be dropped with the v1.6 release of Roundup,
-at which point users will need to run Roundup using either Python v2.6 or v2.7.
+**IMPORTANT** The v1.5.x releases of Roundup will be the last to
+support Python v2.5. Support for Python v2.5 and v2.66 will be dropped
+with the v1.6 release of Roundup. Roundup 1.6 and newer require
+Python v2.7.
 
 Contents:
 
@@ -248,8 +249,8 @@ the email entry in the tracker section::
   # Default: 
   replyto_address = 
 
-Login from a search or after logout works better
-------------------------------------------------
+Login from a search or after logout works better (REQUIRED)
+-----------------------------------------------------------
 
 The login form has been improved to work with some back end code
 changes. Now when a user logs in they stay on the same page where they
@@ -289,6 +290,13 @@ or with::
 the important part is that the action field **must not** include any query
 parameters ('#' includes query params).
 
+One symptom of failing to do this is getting an error:
+
+   Unrecognized scheme in ....
+
+where the .... changes depending on the url path. You can see this
+when logging in from any screen other than the main index.
+
 Option to make adding multiple keywords more convenient
 -------------------------------------------------------
 
@@ -300,7 +308,7 @@ a new checkbox (checked by default) that keeps you on the same page so
 you can add a new keywords one after the other.
 
 To add this to your own tracker, add the following code (prefixed with
-a +) after the entry box for the new keyword::
+a +) after the entry box for the new keyword in html/keyword.item.html::
 
       <tr>
        <th i18n:translate="">Keyword</th>
@@ -328,7 +336,7 @@ property. It is a url which can be used when creating any new item
 (issue, user, keyword ....). It controls the next page displayed after
 creating the item. If '__redirect_to' is not set, then you end up on
 the page for the newly created item. The url value assigned to
-__redirect_to must be under the tracker's base url and must be properly
+__redirect_to must start with the tracker's base url and must be properly
 url encoded.
 
 Helper popups trigger change events on the original page
@@ -549,7 +557,7 @@ page when the search is triggered. This is usually correct since the
 user expects to see the results of the query. But now that
 the code properly checks for duplicate search names, the user should
 stay on the search page if there is an error. To add this to your
-existing index.search.html page, add the following line after the
+existing issue.search.html page, add the following line after the
 hidden field @old-queryname:
 
   <input type="hidden" name="@template" value="index|search"/>