Edgewall Software

Changes between Version 78 and Version 79 of TracUpgrade


Ignore:
Timestamp:
Aug 6, 2010, 12:25:50 AM (11 years ago)
Author:
iroberts@…
Comment:

Spelling, grammar, clarity, style

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v78 v79  
    1111Get the new version as described in TracInstall, or your operating system specific procedure.
    1212
    13 If you already have a 0.11 version of Trac installed via `easy_install`, it might be the easiest to use it also to upgrade you Trac installation.
     13If you already have a 0.11 version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation:
    1414
    1515{{{
     
    1717}}}
    1818
    19 If you do a manual (not operating system specific) upgrade, you should also stop any running Trac server before the installation. Doing "hot" upgrades is not advised, especially not on Windows ([trac:ticket:7625 #7265]).
     19If you do a manual (not operating system-specific) upgrade, you should also stop any running Trac servers before the installation. Doing "hot" upgrades is not advised, especially on Windows ([trac:ticket:7625 #7265]).
    2020
    21 You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac .eggs from former versions.
    22 The location of the site-packages directory depends on the operating system, and the location in which Python was installed. However, the following locations are common:
     21You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac `.egg` files from former versions.
     22The location of the site-packages directory depends on the operating system and the location in which Python was installed. However, the following locations are typical:
    2323 * on Linux: `/usr/lib/python2.X/site-packages`
    2424 * on Windows: `C:\Python2.X\lib\site-packages`
    2525 * on MacOSX: `/Library/Python/2.X/site-packages`
    2626
    27 You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac` (the exact location depends on your platform).
     27You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac`. (The exact location depends on your platform.)
    2828
    29 This cleanup is not mandatory, but it makes it easier to troubleshoot issues later on, as you won't waste your time looking at code or templates from a previous release that are not being used anymore... As usual, make a backup before actually deleting things.
     29This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as you won't waste your time looking at code or templates from a previous release that are not being used anymore... As usual, make a backup before actually deleting things.
    3030
    3131=== 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment
     
    5353}}}
    5454
    55 Note that this procedure will of course leave your `WikiStart` page intact.
     55Note that this procedure will leave your `WikiStart` page intact.
    5656
    5757=== 4. Resynchronize the Trac Environment Against the Source Code Repository ===
     
    6565=== 5. Refresh static resources ===
    6666
    67 If you've setup web server to give out static resources directly (accessed using /chrome/ URL) then you need to refresh them using the same command:
     67If you have set up a web server to give out static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the same command:
    6868{{{
    6969trac-admin /path/to/env deploy /deploy/path
    7070}}}
    71 this will extract static resources and CGI scripts (trac.wsgi, etc) from new Trac version and its plugins into `/deploy/path`.
     71this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
    7272
    73 Some web browsers cache the CSS and Javascript file in a strong way, so you'll perhaps need to refresh the cache of the browsers by a force reload (and tell your users to do so!).
     73Some web browsers cache CSS and Javascript files persistently, so you may need to instruct your users to manually erase the contents of their browser's cache.
    7474
    7575=== 6. Steps specific to a given Trac version  ===
     
    7979
    8080===== SQLite v3.x required =====
    81 SQLite v2.x is no longer supported, if you happen to still use a Trac database using this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details.
     81SQLite v2.x is no longer supported. If you still use a Trac database of this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details.
    8282
    8383===== Multiple Repository Support =====
    84 If you plan to add more repositories to your Trac instance, as this is now possible with the newly introduced multiple repository support, please refer to TracRepositoryAdmin#Migration.
     84The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    8585
    86 This can be of interest even if you only have one repository, as there's now a way to avoid the potentially costly resync check at every request.
     86This may be of interest to users with only one repository, since there's now a way to avoid the potentially costly resync check at every request.
    8787
    8888===== Improved repository synchronization =====
    89 In addition to supporting multiple repositories, a new more efficient method for synchronizing Trac and your repositories was implemented.
     89In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    9090
    9191While you can keep the same synchronization as in 0.11 adding the post-commit hook as outlined in TracRepositoryAdmin#Synchronization and TracRepositoryAdmin#ExplicitSync will allow more efficient synchronization and is more or less required for multiple repositories.
     
    9393Note that if you were using the `trac-post-commit-hook`, ''you're strongly advised to upgrade it'' to the new hook documented in the above references, as the old hook will not work with anything else than the default repository and even for this case, it won't trigger the appropriate notifications.
    9494
    95 ===== Auhtz permission checking =====
     95===== Authz permission checking =====
    9696The authz permission checking has been migrated to a fine-grained permission policy. If you use authz permissions (aka `[trac] authz_file` and `authz_module_name`), you must add `AuthzSourcePolicy` in front of your permission policies in `[trac] permission_policies`. You must also remove `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW` and `LOG_VIEW` from your global permissions (with `trac-admin $ENV permission remove` or the "Permissions" admin panel).
    9797