Commits

Anonymous committed 1a54986

A bit of clean-up for the READMEs and other text files.

Comments (0)

Files changed (5)

 Trac Installation Guide
 =======================
+
 Trac is a lightweight project management tool that is implemented as a
-web-based application. Trac is written in the Python programming language and
-can use SQLite, PostgreSQL or MySQL as database. For HTML rendering, Trac uses 
-the Genshi templating system.
+web-based application. Trac is written in the Python programming
+language and can use SQLite, PostgreSQL or MySQL as database. For HTML
+rendering, Trac uses the Genshi templating system.
 
-
-Note that you should also read the trac/wiki/default-pages/TracInstall 
-documentation file present in the source distribution.
-If you're upgrading an already installed environment, please also read
-trac/wiki/default-pages/TracUpgrade.
-
+Note that you should also read the
+**trac/wiki/default-pages/TracInstall** documentation file present in
+the source distribution.  If you're upgrading an already installed
+environment, please also read trac/wiki/default-pages/TracUpgrade.
 
 
 Requirements
 ------------
+
 To install Trac, the following software packages must be installed:
 
- * Python, version >= 2.4.
+ * Python, version >= 2.5.
  * setuptools, version >= 0.6
  * Genshi, version >= 0.6
- * Optionally, Subversion, version >= 1.1.x and the Subversion SWIG Python 
-   bindings (not PySVN, that's something different).
+ * Optionally, Subversion, version >= 1.1.x and the Subversion SWIG
+   Python bindings (not PySVN, that's something different).
  * One of the following Python bindings, depending on the database used:
-    * pysqlite version 2.x for SQLite 3.x (is part of the standard library 
-      starting with Python 2.5)
+    * pysqlite version 2.x for SQLite 3.x
     * psycopg2 version 2.0.x for the PostgreSQL database
     * MySQLdb, version 1.2.2 for the MySQL database
- * A web server capable of executing CGI/FastCGI scripts, or Apache HTTPD with
-   mod_python or mod_wsgi. (Trac also comes with a standalone server, tracd)
+ * A web server capable of executing CGI/FastCGI scripts, or Apache
+   HTTPD with mod_python or mod_wsgi. (Trac also comes with a
+   standalone server, tracd)
 
-Any of the above python library can usually be installed using easy_install,
-which itself can be installed using the following bootstrap script:
+Any of the above python library can usually be installed using
+easy_install, which itself can be installed using the following
+bootstrap script::
 
   $ wget http://peak.telecommunity.com/dist/ez_setup.py
 
 
 After that, you can do for example: easy_install Genshi
 
-If you're using Python 2.4 and need pysqlite, you can download from
-http://code.google.com/p/pysqlite/downloads/list the Windows installers or the
-tar.gz archive for building from source:
+Your version of Python comes with its own version of pysqlite, however
+if want to use the latest pysqlite package, you can download from
+http://code.google.com/p/pysqlite/downloads/list the Windows
+installers or the tar.gz archive for building from source::
 
   $ tar xvfz <version>.tar.gz
 
 
 Installing Trac
 ---------------
-The command:
+
+The command::
 
   $ python ./setup.py install
 
 will byte-compile the python source code and install it in the
-site-packages directory of your python installation. The directories cgi-bin,
-templates, htdocs and wiki-default are all copied to ``$prefix/share/trac/``.
+site-packages directory of your python installation. The directories
+cgi-bin, templates, htdocs and wiki-default are all copied to
+``$prefix/share/trac/``.
 
-The script will also install the trac-admin command-line tool, used to create
-and maintain project environments. Trac-admin is the command center of Trac.
+The script will also install the trac-admin command-line tool, used to
+create and maintain project environments. Trac-admin is the command
+center of Trac.
 
 Note: you'll need root permissions or equivalent for this step.
 
-To install Trac in a different location, or use other advanced installation
-options, run:
+To install Trac in a different location, or use other advanced
+installation options, run::
 
   $ python ./setup.py --help
 
 
 Installing Trac on Windows
 --------------------------
-If you downloaded the Trac installer (the .exe file), installing is simply a
-matter of running the installer.  After running the installer, configuration
-and installation is the same as for other platforms.
+
+If you downloaded the Trac installer (the .exe file), installing is
+simply a matter of running the installer.  After running the
+installer, configuration and installation is the same as for other
+platforms.
 
 
 Creating a Project Environment
 ------------------------------
-A Trac environment is the backend storage format where Trac stores information
-like wiki pages, tickets, reports, settings, etc. A Trac environment consists
-of the environment configuration file (trac.ini), custom templates, log files,
-and more.
 
-A new Trac environment is created with trac-admin:
+A Trac environment is the backend storage format where Trac stores
+information like wiki pages, tickets, reports, settings, etc. A Trac
+environment consists of the environment configuration file (trac.ini),
+custom templates, log files, and more.
+
+A new Trac environment is created with trac-admin::
 
   $ trac-admin /path/to/projectenv initenv
 
-Note: The user account under which the web server is run needs write permission
-to the environment directory and all the files inside.
+Note: The user account under which the web server is run needs write
+permission to the environment directory and all the files inside.
 
-trac-admin will prompt you for the name of the project, where your subversion
-repository is located, what database you want to use, etc.
+trac-admin will prompt you for the name of the project, where your
+subversion repository is located, what database you want to use, etc.
 
 
 Running the Standalone Server
 -----------------------------
-After having created a Trac environment, you can easily try the web interface
-by running the standalone server tracd:
+
+After having created a Trac environment, you can easily try the web
+interface by running the standalone server ``tracd``::
 
   $ tracd --port 8000 /path/to/projectenv
 
-Then, fire up a browser and visit http://localhost:8000/. You should get a
-simple listing of all environments that tracd knows about. Follow the link
-to the environment you just created, and you should see Trac in action.
+Then, fire up a browser and visit http://localhost:8000/. You should
+get a simple listing of all environments that tracd knows
+about. Follow the link to the environment you just created, and you
+should see Trac in action.
 
 
 Running Trac on a Web Server
 ----------------------------
-Trac provides three options for connecting to a "real" web server: CGI, FastCGI
-and mod_python. For decent performance, it is recommended that you use either
-FastCGI or mod_python.
 
-Please refer to the TracInstall page for details on these setups. You can find
-it either in the wiki of the Trac project you just created, or on the main Trac
-site.
+Trac provides three options for connecting to a "real" web server:
+CGI, FastCGI and mod_python. For decent performance, it is recommended
+that you use either FastCGI or mod_python.
+
+Please refer to the TracInstall page for details on these setups. You
+can find it either in the wiki of the Trac project you just created,
+or on the main Trac site.
 
 
 Using Trac
 ----------
-Once you have your Trac site up and running, you should be able to browse your
-subversion repository, create tickets, view the timeline, etc.
 
-Keep in mind that anonymous (not logged in) users can by default access most
-but not all of the features. You will need to configure authentication and
-grant additional permissions to authenticated users to see the full set of
-features.
+Once you have your Trac site up and running, you should be able to
+browse your subversion repository, create tickets, view the timeline,
+etc.
+
+Keep in mind that anonymous (not logged in) users can by default
+access most but not all of the features. You will need to configure
+authentication and grant additional permissions to authenticated users
+to see the full set of features.
 
 For further documentation, see the TracGuide wiki page.
 
-Release Notes for Trac 0.12 Babel Release
-=========================================
-June 13, 2010
+Release Notes for Trac 0.13 Cell Release
+========================================
+Month xx, 201x
 
 Highlights
 ----------
- * Translation of Trac in your language using Babel (http://babel.edgewall.org)
- * Multiple Repository Support per environment
- * Improved Wiki, more powerful syntax and nicer user interface with 
-   automatic preview in side-by-side editing mode
- * Improved Ticket user interface, with editable comments and 
-   automatic preview
+ * ...
+
 
 Detailed User Visible Changes
 -----------------------------
 
-A detailed view of the API changes since 0.11.x can be found in 
-TracDev/ReleaseNotes/0.12.
+A detailed view of the API changes since 0.12.x can be found in
+http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.13.
 
 Developer-visible changes
 -------------------------
 
-A detailed view of the API changes since 0.11.x can be found in 
-TracDev/ApiChanges/0.12.
+A detailed view of the API changes since 0.12.x can be found in 
+http://trac.edgewall.org/wiki/TracDev/ApiChanges/0.13.
 
 Acknowledgements
 ----------------
+
 Many thanks to the growing number of people who have, and continue to,
-support the project. Also our thanks to all people providing feedback and
-bug reports that helps us making Trac better, easier to use and more
-effective. Starting with the 0.12 release, special thanks go to our
-many translators.
-Without your invaluable help, Trac would not evolve. Thank you all.
+support the project. Also our thanks to all people providing feedback
+and bug reports that helps us making Trac better, easier to use and
+more effective. Starting with the 0.12 release, special thanks go to
+our many translators.  Without your invaluable help, Trac would not
+evolve. Thank you all.
 
-Finally, we offer hope that Trac will prove itself useful to like-minded
-programmers around the world, and that this release will prove an
-improvement over the last version.
+Finally, we offer hope that Trac will prove itself useful to
+like-minded programmers around the world, and that this release will
+prove an improvement over the last version.
 
 Please let us know. :-)
 
- = Testing Readme =
+= Testing Readme =
 
 So, you want to see what's broken?  Eeeexcellent.
 
 If you are running python < 2.4.4, please see the troubleshooting section.
 
- == Quick Start ==
-First thing to do is run the tests.
-If you have genshi and twill installed on your system, you should be able to run the tests like this:
-{{{
-PYTHONPATH=. ./trac/test.py
-}}}
+== Quick Start ==
 
- == Slow Start ==
-If you want to test against specific versions of genshi, twill, pygments, etc., you can set those up like this:
+First thing to do is run the tests.  If you have genshi and twill
+installed on your system, you should be able to run the tests like
+this: {{{ PYTHONPATH=. ./trac/test.py }}}
+
+== Slow Start ==
+
+If you want to test against specific versions of genshi, twill,
+pygments, etc., you can set those up like this:
 {{{
 myworktree/trac
           /pygments-0.8
           /genshi-0.4.4
 }}}
 
-Run `python setup egg_info` in those subdirectories as needed.
-Then you can run:
+Run `python setup egg_info` in those subdirectories as needed.  Then
+you can run:
 {{{
 PYTHONPATH=.:../twill-0.9:../genshi-0.4.4:../pygments-0.8 ./trac/test.py
 }}}
 
-If you want to run just the functional tests, you can do that by running
+If you want to run just the functional tests, you can do that by
+running
 {{{
 PYTHONPATH=.:../twill-0.9:../genshi-0.4.4:../pygments-0.8 ./trac/tests/functional/testcases.py
 }}}
 }}}
 
 
-NOTE: Unlike most unittests, the functional tests share a test fixture across tests.  This means that you can't(*) run just one of the tests by itself.
-But you can run a sub-set of the functional tests:
+NOTE: Unlike most unittests, the functional tests share a test fixture
+across tests.  This means that you can't(*) run just one of the tests
+by itself.  But you can run a sub-set of the functional tests:
 {{{
 PYTHONPATH=.:../twill-0.9:../genshi-0.4.4:../pygments-0.8 ./trac/tests/functional/__init__.py
 PYTHONPATH=.:../twill-0.9:../genshi-0.4.4:../pygments-0.8 ./trac/ticket/tests/functional.py
 PYTHONPATH=.:../twill-0.9:../genshi-0.4.4:../pygments-0.8 ./trac/versioncontrol/tests/functional.py
 }}}
-Note that that there is a set of functional tests that are run regardless of what subset you choose; these tests setup the shared fixture.
 
+Note that that there is a set of functional tests that are run
+regardless of what subset you choose; these tests setup the shared
+fixture.
 
-(*) Unless you modify the code to comment out the other functional tests.  The test fixture is setup and torn down by `FunctionalTestSuite`, and it runs the tests added to it with `_tester` and `_testenv` set in the testcase objects.
 
-The functional tests require subversion, and use a random local port 8000-8999 for the test web server.
+(*) Unless you modify the code to comment out the other functional
+tests.  The test fixture is setup and torn down by
+`FunctionalTestSuite`, and it runs the tests added to it with
+`_tester` and `_testenv` set in the testcase objects.
 
- == Testing output and byproducts ==
+The functional tests require subversion, and use a random local port
+8000-8999 for the test web server.
+
+== Testing output and byproducts ==
+
 There is some logging done:
- - testing.log
+ testing.log ::
     output from trac environment creation, tracd, and some svn commands
- - functional-testing.log
+ functional-testing.log ::
     output from twill
 
-The test fixture is left behind in 'testenv' so you can inspect it when debugging a problem.
+The test fixture is left behind in 'testenv' so you can inspect it
+when debugging a problem.
 {{{
 testenv/htpasswd   -- the password/authentication for the test fixture.  password = username
        /repo       -- the Subversion repository
        /trac       -- the Trac environment
 }}}
-(Note that running the tests again will automatically delete this test environment and create a new one.  If you want to save a test environment, you will need to rename this directory before running the tests again.)
+(Note that running the tests again will automatically delete this test
+environment and create a new one.  If you want to save a test
+environment, you will need to rename this directory before running the
+tests again.)
 
 The command to serve the test environment is:
 {{{
 ./trac/web/standalone.py --basic-auth=trac,testenv/htpasswd, -s \
     --port=8888 testenv/trac
 }}}
-This is particularly useful when a test fails and you want to explore the environment to debug the problem.
+This is particularly useful when a test fails and you want to explore
+the environment to debug the problem.
 
- == Test Coverage ==
-You can now determine statement coverage of unittests and functional tests.  But you'll have to run them separately for now.
+== Test Coverage ==
 
-`figleaf` will need to be on your `PATH`.  Set the `FIGLEAF` environment variable to the figleaf command.
+You can now determine statement coverage of unittests and functional
+tests.  But you'll have to run them separately for now.
 
-Create a figleaf-exclude file with filename patterns to exclude.  For example:
+`figleaf` will need to be on your `PATH`.  Set the `FIGLEAF`
+environment variable to the figleaf command.
+
+Create a figleaf-exclude file with filename patterns to exclude.  For
+example:
 {{{
 /usr/lib/python.*/.*.py
 .*.html
 
 To run without figleaf, be sure to unset `FIGLEAF`.
 
---------------------------------------------------------------------------------
-== TROUBLESHOOTING: ==
+-----------------------------------------------------------------------------
+
+== Troubleshooting ==
 
  1. trac-admin is failing on initenv with this exception:
     {{{
     raise Exception('Failed with exitcode %s running trac-admin with %r' % (retval, args))
 Exception: Failed with exitcode 1 running trac-admin with ('initenv', 'testenv', 'sqlite:db/trac.db', 'svn', '..../testenv/repo')
     }}}
-    This can be caused by not having run `python setup.py egg_info` in the genshi tree.
+    This can be caused by not having run `python setup.py egg_info` in
+    the genshi tree.
 
- 2. Windows needs an implementation of crypt or fcrypt.  Carey Evans' pure
-    python version works, but prints warnings on Python 2.3 (they can be
-    ignored).  See http://carey.geek.nz/code/python-fcrypt/
+ 2. Windows needs an implementation of crypt or fcrypt.  Carey Evans'
+    pure python version works, but prints warnings on Python 2.3 (they
+    can be ignored).  See http://carey.geek.nz/code/python-fcrypt/
 
- 3. Python versions compatibility notes
-   * If using Python >=2.4.0, <2.4.4, you need to backport `unittest` from
-     2.4.4.  If you do not do this, you will get an `AttributeError` regarding
-     `_fixture` being unset on every test.
-   * If using Python >=2.3.0, <2.3.5, you need to backport a few modules for
-     `setuptools` to work properly (`httplib2`, `cookielib`, `_*CookieJar`) and
-     remove the tuple imports to replace with explicit line continuations.
-   * If using Python >=2.3.0, <2.4.0, you need `subprocess`, `unittest`, and
-     `traceback` from 2.4.4.  On Windows you also need to modify `subprocess.py`
-     to use `pywin32` instead of `_subprocess`.  Twill includes a `subprocess`
-     module that will not work in this situation because it is not modified.
-
 Upgrade Instructions
 ====================
 
-A Trac environment sometimes needs to be upgraded before it can be used with
-a new version of Trac. This document describes the steps necessary to upgrade
-an environment.
+A Trac environment sometimes needs to be upgraded before it can be
+used with a new version of Trac. This document describes the steps
+necessary to upgrade an environment.
 
-Note that you should also read the trac/wiki/default-pages/TracUpgrade 
+Note that you should also read the trac/wiki/default-pages/TracUpgrade
 documentation file present in the source distribution.
 
-
-Note that Environment upgrades are not necessary for minor version releases
-unless otherwise noted. For example, there's no need to upgrade a Trac
-environment created with (or upgraded) 0.8.0 when installing 0.8.4 (or any
-other 0.8.x release).
+Note that Environment upgrades are not necessary for minor version
+releases unless otherwise noted. For example, there's no need to
+upgrade a Trac environment created with (or upgraded) 0.8.0 when
+installing 0.8.4 (or any other 0.8.x release).
 
 General Instructions
 --------------------
-Typically, there are four steps involved in upgrading to a newer version of
-Trac:
+
+Typically, there are four steps involved in upgrading to a newer
+version of Trac:
 
 1. Update the Trac Code
 
-Get the new version of Trac, either by downloading an offical release package
-or by checking it out from the Subversion repository.
+Get the new version of Trac, either by downloading an offical release
+package or by checking it out from the Subversion repository.
 
-If you have a source distribution, you need to run
+If you have a source distribution, you need to run::
 
    python setup.py install
 
-to install the new version. If you've downloaded the Windows installer, you
-execute it, and so on.
+to install the new version. If you've downloaded the Windows
+installer, you execute it, and so on.
 
-In any case, if you're doing a major version upgrade (such as from 0.8 to
-0.9), it is highly recommended that you first remove the existing Trac code.
-To do this, you need to delete the `trac` directory from the Python
-`lib/site-packages` directory. You may also want to remove the Trac `cgi-bin`,
-`htdocs` and `templates` directories that are commonly found in a directory
-called `share/trac` (the exact location depends on your platform).
+In any case, if you're doing a major version upgrade (such as from 0.8
+to 0.9), it is highly recommended that you first remove the existing
+Trac code.  To do this, you need to delete the `trac` directory from
+the Python `lib/site-packages` directory. You may also want to remove
+the Trac `cgi-bin`, `htdocs` and `templates` directories that are
+commonly found in a directory called `share/trac` (the exact location
+depends on your platform).
 
 2. Upgrade the Trac Environment
 
-Unless noted otherwise, upgrading between major versions (such as 0.8 and
-0.9) involves changes to the database schema, and possibly the layout of the
-environment. Fortunately, Trac provides automated upgrade scripts to ease the
-pain. These scripts are run via `trac-admin`:
+Unless noted otherwise, upgrading between major versions (such as 0.8
+and 0.9) involves changes to the database schema, and possibly the
+layout of the environment. Fortunately, Trac provides automated
+upgrade scripts to ease the pain. These scripts are run via
+`trac-admin`::
 
    trac-admin /path/to/projenv upgrade
 
 
 3. Update the Trac Documentation
 
-Every Trac environment includes a copy of the Trac documentation for the
-installed version. As you probably want to keep the included documentation in
-sync with the installed version of Trac, `trac-admin` provides a command to
-upgrade the documentation:
+Every Trac environment includes a copy of the Trac documentation for
+the installed version. As you probably want to keep the included
+documentation in sync with the installed version of Trac, `trac-admin`
+provides a command to upgrade the documentation::
 
    trac-admin /path/to/projenv wiki upgrade
 
-Note that this procedure will of course leave your `WikiStart` page intact.
+Note that this procedure will of course leave your `WikiStart` page
+intact.
 
 4. Restart the Web Server
 
 server (note this is not necessary for CGI).
 
 
-The following sections discuss any extra actions that may need to be taken
-to upgrade to specific versions of Trac.
+The following sections discuss any extra actions that may need to be
+taken to upgrade to specific versions of Trac.
+
+From 0.12.x to 0.13.x
+---------------------
+
+See below.
 
 From 0.11.x to 0.12.x
 ---------------------
 
-Really, go read trac/wiki/default-pages/TracUpgrade ...
+For this upgrade, the detailed information can be found either online
+at http://trac.edgewall.org/wiki/TracUpgrade or within the set of
+default wiki pages, part of this source distribution in
+trac/wiki/default-pages/TracUpgrade.
 
 From 0.10.x to 0.11.x
 ---------------------
 
  http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11#Caveats
 
-Also, you should be careful to check that the plugins you depend on have
-been ported to 0.11, as they most probably won't work without adaptation
-due to the numerous internal changes that occurred during 0.11 development.
-Note however that Clearsilver based plugin are still supported.
+Also, you should be careful to check that the plugins you depend on
+have been ported to 0.11, as they most probably won't work without
+adaptation due to the numerous internal changes that occurred during
+0.11 development.  Note however that Clearsilver based plugin are
+still supported.
 
 See: http://trac.edgewall.org/wiki/TracDev/ApiChanges/0.11
 
 
 From 0.9.x to 0.10.x
 --------------------
-Due to some changes in the Wiki syntax, you may notice that certain parts of 
-your pages no longer work as expected:
 
- * Previously, links to images would result in that image being embedded 
-   into the page. Since 0.10, links to images remain plain links. If you 
-   want to embed an image in the page, use the [[Image]] macro.
- * You can no longer use %20 in wiki links to encode spaces. Instead, you 
-   should quote the name containing spaces 
-   (for example, use wiki:"My page" instead of wiki:My%20page.) 
+Due to some changes in the Wiki syntax, you may notice that certain
+parts of your pages no longer work as expected:
 
-Several enhancements have been made to the version control subsystem, in
-particular for the support of scoped repositories has been improved. It is
-recommended that you perform a "trac-admin resync" operation to take
-advantage of these improvements.
+ * Previously, links to images would result in that image being
+   embedded into the page. Since 0.10, links to images remain plain
+   links. If you want to embed an image in the page, use the [[Image]]
+   macro.
+ * You can no longer use %20 in wiki links to encode spaces. Instead,
+   you should quote the name containing spaces (for example, use
+   wiki:"My page" instead of wiki:My%20page.)
 
-Also note that the argument list of the "trac-admin initenv" command has
-changed: there's a new argument for determining the type of version
-control system. The old usage was:
+Several enhancements have been made to the version control subsystem,
+in particular for the support of scoped repositories has been
+improved. It is recommended that you perform a "trac-admin resync"
+operation to take advantage of these improvements.
+
+Also note that the argument list of the "trac-admin initenv" command
+has changed: there's a new argument for determining the type of
+version control system. The old usage was::
 
    initenv <projectname> <db> <repospath> <templatepath>
 
-The new usage is:
+The new usage is::
 
    initenv <projectname> <db> <repostype> <repospath> <templatepath>
 
-If you're using any scripts that automate the creation of Trac environments,
-you will need to update them. If you're using Subversion, specify "svn" for
-the <repostype> argument.
+If you're using any scripts that automate the creation of Trac
+environments, you will need to update them. If you're using
+Subversion, specify "svn" for the <repostype> argument.
 
 
 From 0.9.3 to 0.9.4
 -------------------
-There is a bug in Pysqlite 1.x that causes reports using the "%" character 
-for LIKE clauses or date formatting to fail. You will need to use escape the 
-percent characters with another: "%%".
+
+There is a bug in Pysqlite 1.x that causes reports using the "%"
+character for LIKE clauses or date formatting to fail. You will need
+to use escape the percent characters with another: "%%".
 
 
 From 0.9.x to 0.9.3
 -------------------
-If you are using plugins you might need to upgrade them. See 
-http://trac.edgewall.org/milestone/0.9.3 for further details. 
+
+If you are using plugins you might need to upgrade them. See
+http://trac.edgewall.org/milestone/0.9.3 for further details.
 
 
 From 0.9-beta to 0.9
 --------------------
-If inclusion of the static resources (style sheets, javascript, images) is not
-working, check the value of the `htdocs_location` in trac.ini. For mod_python,
-Tracd and FastCGI, you can simply remove the option altogether. For CGI, you
-should fix it to point to the URL you mapped the Trac `htdocs` directory to.
 
-If you've been using plugins with a beta release of Trac 0.9, or have 
-disabled some of the built-in components, you might have to update the rules
-for disabling/enabling components in trac.ini. In particular, globally 
-installed plugins now need to be enabled explicitly. See the TracPlugins and 
-TracIni wiki pages for more information.
+If inclusion of the static resources (style sheets, javascript,
+images) is not working, check the value of the `htdocs_location` in
+trac.ini. For mod_python, Tracd and FastCGI, you can simply remove the
+option altogether. For CGI, you should fix it to point to the URL you
+mapped the Trac `htdocs` directory to.
 
-If you want to enable the display of all ticket changes in the timeline (the
-Ticket Details option), you now have to explicitly enable that in trac.ini,
-too:
+If you've been using plugins with a beta release of Trac 0.9, or have
+disabled some of the built-in components, you might have to update the
+rules for disabling/enabling components in trac.ini. In particular,
+globally installed plugins now need to be enabled explicitly. See the
+TracPlugins and TracIni wiki pages for more information.
+
+If you want to enable the display of all ticket changes in the
+timeline (the Ticket Details option), you now have to explicitly
+enable that in trac.ini, too::
 
    [timeline]
    ticket_show_details = true
 
 From 0.8.x to 0.9
 -----------------
-mod_python users will need to change the name of the mod_python handler in
-the Apache HTTPD configuration:
+
+mod_python users will need to change the name of the mod_python
+handler in the Apache HTTPD configuration::
 
    from: PythonHandler trac.ModPythonHandler
    to:   PythonHandler trac.web.modpython_frontend
 
-If you have PySQLite 2.x installed, Trac will now try to open your SQLite
-database using the SQLite 3.x file format. The database formats used by
-SQLite 2.8.x and SQLite 3.x are incompatible. If you get an error like "file
-is encrypted or is not a database" after upgrading, then you must convert
-your database file.
+If you have PySQLite 2.x installed, Trac will now try to open your
+SQLite database using the SQLite 3.x file format. The database formats
+used by SQLite 2.8.x and SQLite 3.x are incompatible. If you get an
+error like "file is encrypted or is not a database" after upgrading,
+then you must convert your database file.
 
-To do this, you need to have both SQLite 2.8.x and SQLite 3.x installed (they
-have different filenames so can coexist on the same system). Then use the
-following commands:
+To do this, you need to have both SQLite 2.8.x and SQLite 3.x
+installed (they have different filenames so can coexist on the same
+system). Then use the following commands::
 
    mv trac.db trac2.db
    sqlite trac2.db .dump | sqlite3 trac.db
 
-After testing that the conversion was successful, the `trac2.db` file can be
-deleted. For more information on the SQLite upgrade see
+After testing that the conversion was successful, the `trac2.db` file
+can be deleted. For more information on the SQLite upgrade see
 http://www.sqlite.org/version3.html.
 
-
 From 0.7.x to 0.8
 -----------------
-0.8 adds a new roadmap feature which requires additional permissions. While a
-fresh installation will by default grant `ROADMAP_VIEW` and `MILESTONE_VIEW`
-permissions to anonymous, these permissions have to be granted manually when
-upgrading:
+
+0.8 adds a new roadmap feature which requires additional
+permissions. While a fresh installation will by default grant
+`ROADMAP_VIEW` and `MILESTONE_VIEW` permissions to anonymous, these
+permissions have to be granted manually when upgrading::
 
    trac-admin /path/to/projectenv permission add anonymous MILESTONE_VIEW
    trac-admin /path/to/projectenv permission add anonymous ROADMAP_VIEW
 
 From 0.6.x to 0.7
 -----------------
+
 Trac 0.7 introduced a new database format, requiring manual upgrade.
 
-Previous versions of Trac stored wiki pages, ticket, reports, settings,
-etc. in a single SQLite database file. Trac 0.7 replaces this file
-with a new backend storage format; the 'Trac Environment', which is a
-directory containing an SQLite database, a human-readable configuration file,
-log-files and attachments.
+Previous versions of Trac stored wiki pages, ticket, reports,
+settings, etc. in a single SQLite database file. Trac 0.7 replaces
+this file with a new backend storage format; the 'Trac Environment',
+which is a directory containing an SQLite database, a human-readable
+configuration file, log-files and attachments.
 
 Fear not though, old-style Trac databases can easily be converted to
-Environments using the included `tracdb2env` program as follows:
+Environments using the included `tracdb2env` program as follows::
 
    tracdb2env /path/to/old/project.db /path/to/new/projectenv
 
-`tracdb2env` will create a new environment and copy the information from the
-old database to the new environment. The existing database will not be
-modified.
+`tracdb2env` will create a new environment and copy the information
+from the old database to the new environment. The existing database
+will not be modified.
 
 You also need to update your apache configuration:
 
-Change the line:
+Change the line::
 
    SetEnv TRAC_DB "/path/to/old/project.db"
 
-to:
+to::
 
    SetEnv TRAC_ENV "/path/to/new/projectenv"
 
 
 ----
 
-If you have trouble upgrading Trac, please ask questions on the mailing list:
+If you have trouble upgrading Trac, please ask questions on the
+mailing list:
 
   <http://trac.edgewall.org/wiki/MailingList>
 

trac/htdocs/README

-This directory contains files used by Trac's default clearsilver templates.
+This directory contains files used by Trac's default Genshi templates.
 
 Local modifications to these files might be lost during the installation of 
 a new Trac version. This can be avoided by making a copy of this entire