Mercurial Repository: p/roundup/code: doc/upgrading.txt comparison

comparison doc/upgrading.txt @ 6170:dadcb4fe9f1d

Ading index entries.

author	John Rouillard <rouilj@ieee.org>
date	Fri, 15 May 2020 21:22:41 -0400
parents	de9d602c8ce6
children	5522c950a2e4

comparison

equal deleted inserted replaced

-:6523edf235d4
+:dadcb4fe9f1d
 merged into a more full featured logging config file for
 your tracker if you wish. It will create a new file in the
 current working directory called 'httpd.log' and will rotate
 the log file at 500K and keep two old copies of the file.
+.. index:: Upgrading; 1.5.0 to 1.5.1
 Migrating from 1.5.0 to 1.5.1
 =============================
 User data visibility
 --------------------
 self.client.add_error_message(...)
 The new calls escape the passed string by default and avoid XSS security
 issues.
+.. index:: Upgrading; 1.4.20 to 1.4.21
 Migrating from 1.4.20 to 1.4.21
 ===============================
 The ``_generic.calendar.html`` page of the instance has been updated to include
 to invoke the xmlrpc handler. This allows us to send xml
 data to roundup for other handlers (e.g. REST, SOAP ...)
 in the future.
+.. index:: upgrading; 1.4.19 to 1.4.20
 Migrating from 1.4.19 to 1.4.20
 ===============================
 Roundup used to allow certain HTML-Tags in OK- and Error-messages. Since
 these messages are passed via the URL (due to roundup redirecting after
 If you have not modified any roundup messages, you need not do anything,
 the templates shipped with roundup did not use HTML tags in messages for
 highlighting.
+.. index:: upgrading; 1.4.17 to 1.4.18
 Migrating from 1.4.17 to 1.4.18
 ===============================
 There was a bug in 1.4.17 where files were unlinked from issues if a
 list of files attached to an issue should be files 5, 17, 23 for issue42
 you will set this using
 roundup-admin -i /path/to/your/tracker set issue42 files=5,17,23
+.. index:: upgrading; 1.4.x to 1.4.17
 Migrating from 1.4.x to 1.4.17
 ==============================
 There is a new config-option `migrate_passwords` in section `web` to
 auto-migrate passwords at web-login time to a more secure storage
 if db.security.roleHasSearchPermission(cl,p,role):
 roles.append(role)
 print("        roles may search:", ', '.join(roles))
+.. index:: upgrading; 1.4.x to 1.4.12
 Migrating from 1.4.x to 1.4.12
 ==============================
 Item creation now checks the "Create" permission instead of the "Edit"
 permission for individual properties. If you have modified your tracker
 If you have made local changes to those files you'll need to manually work
 the differences in to your versions or ignore the changes.
+.. index:: upgrading; 1.4.x to 1.4.11
 Migrating from 1.4.x to 1.4.11
 ==============================
 Close potential security hole
 -----------------------------
 The instructions for doing so won't be present in your tracker unless you copy
 the ``_generic.index.html`` template from the roundup distribution in
 ``share/roundup/templates/classic/html`` to your tracker's ``html`` directory.
+.. index:: upgrading; 1.4.x to 1.4.9
 Migrating from 1.4.x to 1.4.9
 =============================
 Customized MailGW Class
 Some previous versions of this upgrading document missed ``method="POST"``
 in the change to the "retire" link in the user management list
 in section `Migrating from 1.4.x to 1.4.7`_.
 Make sure the change is done as listed below in this document.
+.. index:: upgrading; 1.4.x to 1.4.7
 Migrating from 1.4.x to 1.4.7
 =============================
 Several security issues were addressed in this release. Some aspects of your
 # Default: no
 allow_html_file = no
+.. index:: upgrading; 1.4.2 to 1.4.3
 Migrating from 1.4.2 to 1.4.3
 =============================
 If you are using the MySQL backend you will need to replace some indexes
 that may have been created by version 1.4.2.
 with a name ending in "_key_retired_idx". You should then re-add them with
 the same spec except the key column name needs a size. So an index on
 "_user (__retired, _name)" should become "_user (__retired, _name(255))".
+.. index:: upgrading; 1.4.x to 1.4.2
 Migrating from 1.4.x to 1.4.2
 =============================
 You should run the "roundup-admin migrate" command for your tracker once
 you've installed the latest codebase.
 or are using anydbm).
 It's safe to run this even if it's not required, so just get into the
 habit.
+.. index:: upgrading; 1.3.3 to 1.4.0
 Migrating from 1.3.3 to 1.4.0
 =============================
 Value of the "refwd_re" tracker configuration option (section "mailgw")
 following database indexes on the database by hand::
 CREATE INDEX words_by_id ON __words (_textid);
 CREATE UNIQUE INDEX __textids_by_props ON __textids (_class, _itemid, _prop);
+.. index:: upgrading; 1.2.x to 1.3.0
 Migrating from 1.2.x to 1.3.0
 =============================
 1.3.0 Web interface changes
 ---------------------------
 Some of the HTML files in the "classic" and "minimal" tracker templates
 were changed to fix some bugs and clean them up. You may wish to compare
 them to the HTML files in your tracker and apply any changes.
+.. index:: upgrading; 1.1.2 to 1.2.0
 Migrating from 1.1.2 to 1.2.0
 =============================
 1.2.0 Sorting and grouping by multiple properties
 * Templates that diplay new headlines for each group of items with
 equal group properties can now use the modified ``batch.propchanged``
 method that can take several properties which are checked for
 changes. See the example in the classic template which makes use of
 ``batch.propchanged``.
+.. index:: upgrading; 1.1.0 to 1.1.1
 Migrating from 1.1.0 to 1.1.1
 =============================
 1.1.1 "Clear this message"
 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!
+.. index:: upgrading; 1.0.x to 1.1.0
 Migrating from 1.0.x to 1.1.0
 =============================
 1.1 Login "For Session Only"
 ----------------------------
 tal:content="structure string:$m <br/ > " />
 <a class="form-small" tal:attributes="href string:issue${context/id}"
 i18n:translate="">clear this message</a>
 </p>
+.. index:: upgrading; 0.8.x to 1.0
 Migrating from 0.8.x to 1.0
 ===========================
 1.0 New Query Permissions
 so it looks like::
 for cl in 'issue', 'file', 'msg', 'keyword':
+.. index:: upgrading; 0.8.0 to 0.8.3
 Migrating from 0.8.0 to 0.8.3
 =============================
 0.8.3 Nosy Handling Changes
 ---------------------------
 directory of the source to your tracker's ``templates`` directory.
 If you have modified the ``nosyreaction.py`` file from the standard
 version, you will need to roll your changes into the new file.
+.. index:: upgrading; 0.7.1 to 0.8.0
 Migrating from 0.7.1 to 0.8.0
 =============================
 You *must* fully uninstall previous Roundup version before installing
 See the `administration guide`_ for information about configuring the new
 logging implemented in 0.8.0.
+.. index:: upgrading; 0.7.2 to 0.7.3
 Migrating from 0.7.2 to 0.7.3
 =============================
 0.7.3 Configuration
 -------------------
 directory defaults to the ``TEMPLATES`` configuration variable. You may
 define a new variable, ``STATIC_FILES`` which overrides this value for
 static files.
+.. index:: upgrading; 0.7.0 to 0.7.2
 Migrating from 0.7.0 to 0.7.2
 =============================
 0.7.2 DEFAULT_TIMEZONE is now required
 --------------------------------------
 # You may specify a different default timezone, for use when users do not
 # choose their own in their settings.
 DEFAULT_TIMEZONE = 0            # specify as numeric hour offest
+.. index:: upgrading; 0.7.0 to 0.7.1
 Migrating from 0.7.0 to 0.7.1
 =============================
 0.7.1 Permission assignments
 db.security.addPermissionToRole('Anonymous', p)
 next to the existing ``'User'`` lines for the Permissions you wish to
 assign to the anonymous user.
+.. index:: upgrading; versions earlier than 0.7
 Migrating from 0.6 to 0.7
 =========================
 0.7.0 Permission assignments

Mercurial > p > roundup > code

comparison doc/upgrading.txt @ 6170:dadcb4fe9f1d