Commits

Anonymous committed 0af1458

Preparing for release

  • Participants
  • Parent commits 4776fa3
  • Branches trunk

Comments (0)

Files changed (22)

+Trac 0.10-rc1  (Sep 22, 2006)
+http://svn.edgewall.org/repos/trac/tags/trac-0.10rc1
+
+ Trac 0.10 contains a great number of new features, improvements and
+ bug fixes. The following list contains only a few highlights:
+
+ * Support for spam protection.
+ * Advanced diff support.
+ * InterWiki and InterTrac support.
+ * Improved notification system.
+ * WSGI Used as web server protocol.
+
+ A more complete list of new features can be found in the RELEASE file.
+ The complete list of closed tickets can be found here:
+   http://trac.edgewall.org/query?status=closed&milestone=0.10
+
 Trac 0.10-beta1  (Aug 28, 2006)
 http://svn.edgewall.org/repos/trac/tags/trac-0.10b1
 
-Release Notes for Trac 0.10b1
-=============================
-August 28, 2006
+Release Notes for Trac 0.10rc1
+==============================
+September 22, 2006
 
-We're happy to announce the Trac 0.10b1 release, available from:
+We're happy to announce the Trac 0.10rc1 release, available from:
 
   http://trac.edgewall.org/wiki/TracDownload
 
-This is a beta release, which means that the Trac developers feel that this
-release is stable enough for for serious testing. While we feel that this
-release is stable we do not recommend to use this release in production. If
-no serious bugs are found the final stable 0.10 release will be released in
-a couple of days.
+This is a release candidate, which means that the Trac developers feel
+that this release is ready for production use, so we encourage people to
+test this release thoroughly. If no serious bugs are found the final
+stable 0.10 release will be released on Monday.
 
 For questions, comments and user discussions, please use the Trac mailing
 list. List information, subscription and archive available at:
 
 Advanced diff support
 ---------------------
-The TracRevisionLog view can now be used to select two arbitrary revisions
-of a given path in the repository and see the differences between them, in
-the familiar TracChangeset view.
+The TracRevisionLog view can now be used to select two arbitrary
+revisions of a given path in the repository and see the differences
+between them, in the familiar TracChangeset view.
 
 A related change is the possibility to navigate through a sequence of
 restricted changesets. A restricted changeset is the subset of changes
 within a changeset inside a given directory. One can easily start
-navigating such a sequence by following the new Last Change navigation link
-present for the currently browsed path.
+navigating such a sequence by following the new Last Change navigation
+link present for the currently browsed path.
 
-It's now also possible to compare two arbitrary paths at any revision. This
-can be used to check the differences between a tagged version and trunk, or
-to review the set of differences between two branches.
+It's now also possible to compare two arbitrary paths at any revision.
+This can be used to check the differences between a tagged version and
+trunk, or to review the set of differences between two branches.
+
+Other enhancements have been made to the version control subsystem, in
+particular the support of scoped repositories has been improved. You
+should therefore perform a trac-admin resync operation.
 
 InterWiki and InterTrac support
 -------------------------------
 An InterWiki link can be used to refer to a Wiki page located on another
-Wiki system, and by extension, to any object located on any other Web site,
-as long as simple URL mapping is possible.
+Wiki system, and by extension, to any object located on any other Web
+site, as long as simple URL mapping is possible.
 
-An InterTrac link can be used for referring to a Trac resource (Wiki page,
-changeset, ticket, ...) on an other Trac environment. This makes it easier
-to work with multiple separate projects, and seamlessly refer to resources
-from one Trac to another.
+An InterTrac link can be used for referring to a Trac resource (Wiki
+page, changeset, ticket, ...) on an other Trac environment. This makes it
+easier to work with multiple separate projects, and seamlessly refer to
+resources from one Trac to another.
 
 Improved modularity
 -------------------
 experimental support for the MySQL database.
 
 As for the version control systems, Trac still features best of breed
-Subversion support, but the Subversion bindings and libraries are no longer
-mandatory for using Trac itself. Other version control systems can be
-supported by external plugins.
+Subversion support, but the Subversion bindings and libraries are no
+longer mandatory for using Trac itself. Other version control systems can
+be supported by external plugins.
 
 Improved notification system
 ----------------------------
-The encoding for emails sent out by Trac can now be confiured. This may
+The encoding for emails sent out by Trac can now be configured. This may
 decrease email size and can avoid useless encoding for western languages
 that make some touchy SMTP servers bounce the notifications.
 
   http://trac.edgewall.org/wiki/SpamFilter
 
 This plugin implements a number of different strategies for testing
-content, such as regular expression matching, IP blacklisting, and Akismet
-queries.
+content, such as regular expression matching, IP blacklisting, and
+Akismet queries.
 
 WSGI used as web server protocol
-
-Trac now uses WSGI (the "Python Web Server Gateway Interface") internally.
-While Trac continues to provide builtin support for CGI, FastCGI and
-mod_python, as well as the standalone server "tracd", you can now take
-advantage of the WSGI support to use Trac in other setups, such as Twisted,
-Paste, SCGI, or ISAPI.
+--------------------------------
+Trac now uses WSGI (the "Python Web Server Gateway Interface")
+internally. While Trac continues to provide builtin support for CGI,
+FastCGI and mod_python, as well as the standalone server "tracd", you can
+now take advantage of the WSGI support to use Trac in other setups, such
+as Twisted, Paste, SCGI, or ISAPI.
 
 Lots of minor improvements
 --------------------------
-
 To the Wiki syntax
 
 Numerous improvements have been made in the WikiFormatting syntax:
  * Added more robust parsing and formatting of Wiki lists and robust
    coupling of lists and quotes.
  * Improved the way external links are displayed.
- * Lots of new ways to refer to specific repository views (diff:from//to,
-   log:, [x:y], rx:y)
+ * Lots of new ways to refer to specific repository views (diff:from//
+   to, log:, [x:y], rx:y)
  * htdocs:, useful for referring to local resources in TracStandalone
  * MoinMoin-style syntax for description lists
  * Removed support for direct embedding of images using links: use the
 ------------------
 Trac used to handle text content by using str objects, in which Unicode
 characters were represented using UTF-8 encoding. This lead to various
-problems with most non-western languages. We now use the dedicated unicode
-datatype to consistently handle text written in any language.
+problems with most non-western languages. We now use the dedicated
+unicode datatype to consistently handle text written in any language. See
+also TracDev/UnicodeGuidelines.
 
-Better way to programatically generate HTML fragments
------------------------------------------------------
-Trac now provides utility code to programmatically generate HTML snippets.
-This can be used in the various places where Trac expects plugins to return
-small fragments of HTML bypassing the template system. These utilities can
-be found in the trac.util.html module.
+Better way to programmatically generate HTML fragments
+------------------------------------------------------
+Trac now provides utility code to programmatically generate HTML
+snippets. This can be used in the various places where Trac expects
+plugins to return small fragments of HTML bypassing the template system.
+These utilities can be found in the trac.util.html module.
 
 Unit test framework for email notifications
 -------------------------------------------
-Email notifications can now be validated; unit tests include a private SMTP
-server and helper methods to extract and decode email data.
+Email notifications can now be validated; unit tests include a private
+SMTP server and helper methods to extract and decode email data.
+
+Internal API changes
+--------------------
+A detailed view of the API changes since 0.9.x can be found in TracDev/
+ApiChanges/0.10.
 
 Acknowledgements
 ================
 """
 __docformat__ = 'epytext en'
 
-__version__ = '0.10b1'
+__version__ = '0.10rc1'
 __url__ = 'http://trac.edgewall.org/'
 __copyright__ = '(C) 2003-2006 Edgewall Software'
 __license__ = 'BSD'

wiki-default/InterMapTxt

 DebianPackage    http://packages.debian.org/
 Dictionary       http://www.dict.org/bin/Dict?Database=*&Form=Dict1&Strategy=*&Query=
 Google           http://www.google.com/search?q=
-GoogleGroups     http://groups.google.com/groups?q=
+GoogleGroups     http://groups.google.com/group/$1/msg/$2        # Message $2 in $1 Google Group
 JargonFile       http://downlode.org/perl/jargon-redirect.cgi?term=
 MeatBall         http://www.usemod.com/cgi-bin/mb.pl?
 MetaWiki         http://sunir.org/apps/meta.pl?

wiki-default/InterWiki

 located in any other Web application, provided a simple URL 
 mapping can be done.
 
+At the extreme, InterWiki prefixes can even be used to simply introduce
+links to new protocols, such as `tsvn:` used by TortoiseSvn.
+
 == Link Syntax ==
 
 {{{
 }}}
 
 The link is composed by the targeted Wiki (or system) name,
-followed by a colon (e.g. {{{MeatBall:}}}),
+followed by a colon (e.g. `MeatBall:`),
 followed by a page specification in the target.
-Note that, as for InterTrac prefixes, InterWiki prefixes are case insensitive.
+Note that, as for InterTrac prefixes, '''InterWiki prefixes are case insensitive'''.
 
-The target Wiki URL is looked up in a the InterMapTxt wiki page, 
-modelled after
-[http://www.usemod.com/cgi-bin/mb.pl?InterMapTxt MeatBall:InterMapTxt].
+The target Wiki URL is looked up in the InterMapTxt wiki page, 
+modelled after MeatBall:InterMapTxt.
 
 In addition to traditional InterWiki links, where the target
 is simply ''appended'' to the URL, 
 In addition, an optional comment is allowed after the mapping.
 ----
 {{{
-PEP     http://www.python.org/peps/pep-$1.html                                       # Python Enhancement Proposal $1 
+PEP      http://www.python.org/peps/pep-$1.html           # Python Enhancement Proposal $1 
 Trac-ML  http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/$1  # Message $1 in Trac Mailing List
 
+tsvn     tsvn:                                            # Interact with TortoiseSvn
 ...
 MeatBall http://www.usemod.com/cgi-bin/mb.pl?
 MetaWiki http://sunir.org/apps/meta.pl?
 }}}
 
 Then, 
- * `MoinMoin:InterWikiMap` should be rendered as 
-   [http://moinmoin.wikiwikiweb.de/InterWikiMap MoinMoin:InterWikiMap]
+ * `MoinMoin:InterWikiMap` should be rendered as MoinMoin:InterWikiMap
    and the ''title'' for that link would be "!InterWikiMap in !MoinMoin"
- * {{{Trac-ML:4346}}} should be rendered as 
-   [http://thread.gmane.org/gmane.comp.version-control.subversion.trac.general/4346 Trac-ML:4346]
+ * `Trac-ML:4346` should be rendered as Trac-ML:4346
    and the ''title'' for that link would be "Message 4346 in Trac Mailing List"
 
 ----
-=== Temporary notice (delete this when we sync) ===
-About full links vs. having the InterWiki link itself. 
-
-Well, I'm not sure about that, since those InterWiki prefixes ''are'' (or will be when we sync) present in the default InterMapTxt, so those examples will work until the InterMapTxt gets locally edited, at which point it won't be a surprise that this links don't work anymore... OTOH, if those examples ''still'' work after the prefixes have been removed, this can also be a bit surprising ;)
-----
+See also: InterTrac, InterMapTxt

wiki-default/TracFastCgi

 </IfModule>
 LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so
 }}}
-Setting `FastCgiIpcDir` is optional if the default is suitable.
+Setting `FastCgiIpcDir` is optional if the default is suitable. Note that the `LoadModule` line must be after the `IfModule` group.
 
 Configure `ScriptAlias` or similar options as described in TracCgi, but
 calling `trac.fcgi` instead of `trac.cgi`.
 # Use negative lookahead, matching all requests that ask for any resource under /trac, EXCEPT in
 # /trac/chrome/common, and use FastCGI for those
 $HTTP["url"] =~ "^/trac(?!/chrome/common)" {
-# If you have previous fastcgi.server declarations for applications other than Trac, use += here
-# instead of = so you won't overwrite them
+# Even if you have other fastcgi.server declarations for applications other than Trac, do NOT use += here
 fastcgi.server = ("/trac" =>
                    ("trac" =>
                      ("socket" => "/tmp/trac-fastcgi.sock",
 
   If nothing else helps and trac.fcgi doesn't start with lighttpd settings __server.username = "www-data"__, __server.groupname = "www-data"__, then in the `bin-environment` section set `PYTHON_EGG_CACHE` to the home directory of `www-data` or some other directory accessible to this account for writing.
 
+
+== Simple LiteSpeed Configuration ==
+
+The FastCGI front-end was developed primarily for use with alternative webservers, such as [http://www.litespeedtech.com/ LiteSpeed].
+
+LiteSpeed web server is an event-driven asynchronous Apache replacement designed from the ground-up to be secure, scalable, and operate with minimal resources. LiteSpeed can operate directly from an Apache config file and is targeted for business-critical environments.
+
+Setup
+
+1) Please make sure you have first have a working install of a Trac project. Test install with “tracd” first.
+
+2) Create a Virtual Host for this setup. From now on we will refer to this vhost as TracVhost. For this tutorial we will be assuming that your trac project will be accessible via:
+
+{{{
+http://yourdomain.com/trac/
+}}}
+
+3) Go “TracVhost → External Apps” tab and create a new “External Application”.
+
+{{{
+Name: MyTracFCGI	
+Address: uds://tmp/lshttpd/mytracfcgi.sock
+Max Connections: 10
+Environment: TRAC_ENV=/fullpathto/mytracproject/ <--- path to root folder of trac project
+Initial Request Timeout (secs): 30
+Retry Timeout (secs): 0
+Persistent Connection	Yes
+Connection Keepalive Timeout: 30
+Response Bufferring: No	
+Auto Start: Yes
+Command: /usr/share/trac/cgi-bin/trac.fcgi  <--- path to trac.fcgi
+Back Log: 50
+Instances: 10
+}}}
+
+4) Optional. If you need to use htpasswd based authentication. Go to “TracVhost → Security” tab and create a new security “Realm”.
+
+{{{
+DB Type: Password File
+Realm Name: MyTracUserDB               <--- any name you wish and referenced later
+User DB Location: /fullpathto/htpasswd <--- path to your htpasswd file
+}}}
+
+If you don’t have a htpasswd file or don’t know how to create the entries within one, go to http://sherylcanter.com/encrypt.php, to generate the user:password combos.
+
+5) Go to “PythonVhost → Contexts” and create a new “FCGI Context”.
+
+{{{
+URI: /trac/                              <--- URI path to bind to python fcgi app we created	
+Fast CGI App: [VHost Level] MyTractFCGI  <--- select the trac fcgi extapp we just created
+Realm: TracUserDB                        <--- only if (4) is set. select ream created in (4)
+}}}
+
+6) Modify /fullpathto/mytracproject/conf/trac.ini
+
+{{{
+#find/set base_rul, url, and link variables
+base_url = http://yourdomain.com/trac/ <--- base url to generate correct links to
+url = http://yourdomain.com/trac/      <--- link of project
+link = http://yourdomain.com/trac/     <--- link of graphic logo
+}}}
+
+7) Restart LiteSpeed, “lswsctrl restart”, and access your new Trac project at: 
+
+{{{
+http://yourdomain.com/trac/
+}}}
+
 ----
 See also TracCgi, TracModPython, TracInstall, TracGuide

wiki-default/TracImport

 == Other ==
 
 Since trac uses a SQL database to store the data, you can import from other systems by examining the database tables. Just go into [http://www.sqlite.org/sqlite.html sqlite] command line to look at the tables and import into them from your application.
+
+=== Using a comma delimited file - CSV ===
+See [http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py] for details.  This approach is particularly useful if one needs to enter a large number of tickets by hand. (note that the ticket type type field, (task etc...) is also needed for this script to work with more recent Trac releases)

wiki-default/TracIni

 
 == [diff] ==
 || `tab_width` || ''deprecated since 0.9 in favor of the `tab_width` option in the `[mimeviewer]` section'' ||
-
+ 
 == [project] ==
 || `name`   || Project name ||
 || `descr`  || Short project description ||
 || `default_milestone` || Default milestone for newly created tickets ||
 || `default_component` || Default component for newly created tickets ||
 || `default_type`      || Default type for newly created tickets ||
-|| `restrict_owner`    || Make the owner field of tickets use a drop-down menu (''since 0.9''). See [wiki:TracTickets#AssigntoasDropDownList AssignToAsDropDownList] ||
+|| `restrict_owner`    || Make the owner field of tickets use a drop-down menu (''since 0.9''). See [wiki:TracTickets#Assign-toasDrop-DownList AssignToAsDropDownList] ||
 
 == [ticket-custom] ==
 Creates [wiki:TracTicketsCustomFields user-defined ticket fields].
 
 See also: TracPlugins
 
+== [changeset] ==
+(''since 0.10'')
+
+|| `max_diff_bytes` || A limit for the sum of the size of all old ''and'' new files involved in a changeset. [[br]] Note that when requesting a diff precisely on a very big file (e.g. by the use of the ''Last Change'' link), the size limit will ''not'' be taken into account and the diffs will always be computed. ||
+
 ----
 See also: TracGuide, TracAdmin, TracEnvironment

wiki-default/TracInstall

  * [http://www.python.org/ Python], version >= 2.3.
    * For RPM-based systems you might also need the `python-devel` and `python-xml` packages.
    * If you want to use Trac with Subversion on Windows, note that there are no precompiled Subversion bindings for Python 2.4, so you probably need Python 2.3.
+    * 2006-09-20: This seems to be no longer true, see http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91. For subversion 1.4.0 python 2.4 binary bindings are available.
  * [http://www.clearsilver.net/ ClearSilver], version >= 0.9.3
    * With python-bindings (`./configure --with-python=/usr/bin/python`)
  * You also need a database system and the corresponding python drivers for it.
 === For SQLite ===
 
  * [http://www.sqlite.org/ SQLite], version 2.8.x or 3.x (preferred)
- * [http://pysqlite.initd.org/ PySQLite], version 1.x (for SQLite 2.x) or version 2.x (for SQLite 3.x). For details see [http://trac.edgewall.org/wiki/PySqlite PySqlite]
+ * [http://pysqlite.org/ PySQLite], version 1.x (for SQLite 2.x) or version 2.x (for SQLite 3.x). For details see [http://trac.edgewall.org/wiki/PySqlite PySqlite]
 
 ''Note: Versions of Trac prior to 0.9 do '''not''' work with PySQLite 2.x.''
 

wiki-default/TracInterfaceCustomization

 If you absolutely need to use modified templates, copy the template files from the default templates directory (usually in found in `$prefix/share/trac/templates`) into the `templates` directory of the project environment. Then modify those copies to get the desired results.
 
 ----
-See also TracGuide, TracIni
+See also TracGuide, TracIni

wiki-default/TracModPython

 LoadModule python_module modules/mod_python.so
 }}}
 
- ''Note: The exact path to the module depends on how the HTTPD installation is layed out.''
+ ''Note: The exact path to the module depends on how the HTTPD installation is laid out.''
 
 You can test your mod_python installation by adding the following to your httpd.conf.  You should remove this when you are done testing for security reasons.
 {{{
 
 If the <Location /> directive is used, setting the `DocumentRoot` may result in a ''403 (Forbidden)'' error. Either remove the `DocumentRoot` directive, or make sure that accessing the directory it points is allowed (in a corresponding `<Directory>` block).
 
+Using <Location /> together with `SetHandler` resulted in having everything handled by mod_python, which leads to not being able download any CSS or images/icons. I used <Location /trac> `SetHandler None` </Location> to circumvent the problem, though I do not know if this is the most elegant solution.
+
 === Using .htaccess ===
 
 Although it may seem trivial to rewrite the above configuration as a directory in your document root with a `.htaccess` file, this does not work. Apache will append a "/" to any Trac URLs, which interferes with its correct operation.
 
 === Subversion issues ===
 
-If you get the following Trac Error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive (The better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.)
+If you get the following Trac Error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive. (The better way is to add a link to the bindings in the Python `site-packages` directory, or create a `.pth` file in that directory.)
 
 If this is not the case, it's possible that you're using Subversion libraries that are binary incompatible with the apache ones (an incompatibility of the `apr` libraries is usually the cause). In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`).
 

wiki-default/TracPermissions

 
 To enable all privileges for a user, use the `TRAC_ADMIN` permission. Having `TRAC_ADMIN` is like being `root` on a *NIX system, it will allow you perform any operation.
 
-Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac (not that the privilege names are case-sensitive):
+Otherwise, individual privileges can be assigned to users for the various different functional areas of Trac (note that the privilege names are case-sensitive):
 
 === Repository Browser ===
 
 In the same way, privileges granted to the special user ''authenticated'' will apply to any authenticated (logged in) user.
 
 ----
-See also: FineGrainedPermissions, TracAdmin, TracGuide
+See also: TracAdmin, TracGuide and [http://trac.edgewall.org/wiki/FineGrainedPermissions FineGrainedPermissions]

wiki-default/TracStandalone

 Note: If you use the above script you must use the --auth option to tracd, not --basic-auth, and you must set the realm in the --auth value to 'trac' (without the quotes). Example usage (assuming you saved the script as trac-digest.py):
 
 {{{
-python trac-digest.py -u username -p password > c:\digest.txt
+python trac-digest.py -u username -p password >> c:\digest.txt
 python tracd --port 8000 --auth proj_name,c:\digest.txt,trac c:\path\to\proj_name
 }}}
 
 
 ----
 See also: TracInstall, TracCgi, TracModPython, TracGuide
+
+----
+'''Translation:'''
+ * [https://opensvn.csie.org/traccgi/trac_rus/wiki/StandAloneTracForTeapot Russian] (перевод на Русский)

wiki-default/TracSyntaxColoring

 
 ''(1) Ruby highlighting is not included in the Enscript distribution.  Highlighting rules for Ruby can be obtained from: http://neugierig.org/software/ruby/
 
-''(2) C# highlighting is not included in the Enscript distribution.  Highlighting rules for Ruby can be obtained from: http://wiki.hasno.info/index.php/Csharp.st
+''(2) C# highlighting is not included in the Enscript distribution.  Highlighting rules for C# can be obtained from: http://wiki.hasno.info/index.php/Csharp.st
 
 == Extra Software ==
  * GNU Enscript -- http://directory.fsf.org/GNU/enscript.html

wiki-default/TracTickets

 
 '''Note:''' Versions of Trac prior to 0.9 did not have the ''type'' field, but instead provided a ''severity'' field and different default values for the ''priority'' field. This change was done to simplify the ticket model by removing the somewhat blurry distinction between ''priority'' and ''severity''. However, the old model is still available if you prefer it: just add/modify the default values of the ''priority'' and ''severity'', and optionally hide the ''type'' field by removing all the possible values through [wiki:TracAdmin trac-admin].
 
+'''Note:''' the ''type'' (TicketTypes), ''component'' (TicketComponent), ''version'' (TicketVersion), ''priority'' (TicketPriority) and ''severity'' (TicketSeverity) fields can all be managed through [wiki:TracAdmin trac-admin].
 
 == Changing and Commenting Tickets ==
 

wiki-default/TracTicketsCustomFields

    * value: Default value (0 or 1).
    * order: Sort order placement.
  * '''select''': Drop-down select box. Uses a list of values.
+   * label: Descriptive label.
    * options: List of values, separated by '''|''' (vertical pipe).
    * value: Default value (Item #, starting at 0).
    * order: Sort order placement.

wiki-default/TracUpgrade

 
 Get the new version of Trac, either by downloading an offical release package or by checking it out from the [http://projects.edgewall.com/trac/wiki/SubversionRepository Subversion repository].
 
+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`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac` (the exact location depends on your platform).
+
 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.
 
-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`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac` (the exact location depends on your platform).
-
 === 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 [wiki:TracEnvironment environment directory]. Fortunately, Trac provides automated upgrade scripts to ease the pain. These scripts are run via [wiki:TracAdmin trac-admin]:
  * 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`.)
 
+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 [TracAdmin#InteractiveMode trac-admin] '''`resync`''' operation to take advantage of these improvements.
+
 == 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: "%%".

wiki-default/WikiFormatting

 
 The Trac wiki supports the following font styles:
 {{{
- * '''bold''', '''!''' can be bold too'''
+ * '''bold''', '''!''' can be bold too''', and '''! '''
  * ''italic''
  * '''''bold italic'''''
  * __underline__
 }}}
 
 Display:
- * '''bold''', '''!''' can be bold too'''
+ * '''bold''', '''!''' can be bold too''', and '''! '''
  * ''italic''
  * '''''bold italic'''''
  * __underline__
 
 Notes:
  * `{{{...}}}` and {{{`...`}}} commands not only select a monospace font, but also treat their content as verbatim text, meaning that no further wiki processing is done on this text.
- * {{{ ! }}} tells wiki parser to not take the following characters as wiki format.
+ * {{{ ! }}} tells wiki parser to not take the following characters as wiki format, so pay attention to put a space after !, e.g. when ending bold.
 
 == Headings ==
 
  * Tickets: #1 or ticket:1
  * Reports: {1} or report:1
  * Changesets: r1, [1] or changeset:1
- * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable@1:3
- * Wiki pages: CamelCase or wiki:CamelCase
- * Milestones: milestone:1.0 or milestone:"End-of-days Release"
- * Files: source:trunk/COPYING
- * Wiki Attachments: attachment:sample_attachment.txt
- * Ticket Attachments: attachment:ticket:944:attachment.1073.diff
- * A specific file revision: source:/trunk/COPYING@200
- * A particular line of a specific file revision: source:/trunk/COPYING@200#L25
- * A filename with embedded space: source:"/trunk/README FIRST"
+ * ...
 }}}
 
 Display:
  * Tickets: #1 or ticket:1
  * Reports: {1} or report:1
  * Changesets: r1, [1] or changeset:1
- * Revision Logs: r1:3, [1:3] or log:branches/0.8-stable@1:3
- * Wiki pages: CamelCase or wiki:CamelCase
- * Milestones: milestone:1.0 or milestone:"End-of-days Release"
- * Files: source:trunk/COPYING
- * Wiki Attachments: attachment:sample_attachment.txt
- * Ticket Attachments: attachment:ticket:944:attachment.1073.diff
- * A specific file revision: source:/trunk/COPYING@200
- * A particular line of a specific file revision: source:/trunk/COPYING@200#L25
- * A filename with embedded space: source:"/trunk/README FIRST"
+ * ... 
 
 See TracLinks for more in-depth information.
 
 
 == Images ==
 
-Urls ending with `.png`, `.gif` or `.jpg` are automatically interpreted as image links, and converted to `<img>` tags.
+Urls ending with `.png`, `.gif` or `.jpg` are no longer automatically interpreted as image links, and converted to `<img>` tags.
 
-Example:
-{{{
-http://www.edgewall.com/gfx/trac_example_image.png
-}}}
-
-Display:
-
-http://www.edgewall.com/gfx/trac_example_image.png
-
-However, this doesn't give much control over the display mode. This way of inserting images is deprecated in favor of the more powerful `Image` macro (see WikiMacros).
+You now have to use the ![[Image]] macro (see below).
 
 
 == Macros ==
 #!perl
 my ($test) = 0;
 if ($test > 0) {
-echo "hello";
+    print "hello";
 }
 }}}
 

wiki-default/WikiProcessors

 
 
 == Advanced Topics: Developing Processor Macros ==
-Developing processors is no different than WikiMacros. In fact they work the same way, only the usage syntax differs. See WikiMacros for more information.
+Developing processors is no different from WikiMacros. In fact they work the same way, only the usage syntax differs. See WikiMacros for more information.
 
 '''Example:''' (''Restructured Text Processor''):
 {{{
+#!python
 from docutils.core import publish_string
 
 def execute(hdf, text, env):

wiki-default/WikiRestructuredText

 
 
 ----
-See also: WikiRestructuredTextLinks, WikiProcessors, WikiFormatting
+See also: WikiRestructuredTextLinks, WikiProcessors, WikiFormatting

wiki-default/WikiStart

-= Welcome to Trac 0.10b1 =
+= Welcome to Trac 0.10rc1 =
 
 Trac is a '''minimalistic''' approach to '''web-based''' management of
 '''software projects'''. Its goal is to simplify effective tracking and handling of software issues, enhancements and overall progress.