Edgewall Software

Changes between Version 14 and Version 15 of TracDev/ReleaseNotes/0.10


Ignore:
Timestamp:
Aug 26, 2006, 10:41:00 PM (18 years ago)
Author:
Christopher Lenz
Comment:

Fill in placeholders, and some improvements

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/ReleaseNotes/0.10

    v14 v15  
    11= Release Notes for Trac [milestone:0.10] =
    2 
    3 == Improved modularity ==
    4 
    5 Trac now supports database and version control backends as third-party plugins.
    6 
    7 It is now easier to add support for new database backends.
    8 In addition to the already existing support for SQLite and PostgreSQL,
    9 Trac now features experimental support for the MySQL database.
    10 
    11 As for the version control systems, Trac still features best of breed
    12 Subversion support, but the dependency on the Subversion bindings and
    13 libraries is no longer mandatory.
    14 This will make life far easier for those wanting to use Trac without Subversion.
    15 Other version system backends are supported by the way of external plugins.
    16 
    17 == Improved notification system ==
    18 
    19 MIME encoding scheme can be selected: base64 (default),
    20 quoted-printable or none. This feature decreases email size and avoids useless
    21 encodings for western languages that make some touchy SMTP servers bounce
    22 the notifications.
    23 
    24 Improved support for local network installations supporting local email
    25 addresses (addresses without a domain name) and default domain name.
    26 
    27 Support for both visible and blind carbon copies.
    282
    293== Advanced diff support ==
     
    359A related change is the possibility to navigate through a sequence
    3610of ''restricted'' changesets. A ''restricted'' changeset is the subset
    37 of changes within a changeset that are corresponding to a given path.
    38 One can easily start navigating such a sequence by following the new
    39 ''Last Change'' navigation link present for the currently browsed path.
     11of changes within a changeset inside a given directory. One can easily
     12start navigating such a sequence by following the new  ''Last Change''
     13navigation link present for the currently browsed path.
    4014
    41 It's even possible to compare two arbitrary paths (at any given revision).
    42 This can be useful to check the differences between a tagged version and
    43 the ''trunk'', or to review the set of differences between two branches...
     15It's now also possible to compare two arbitrary paths at any revision. This
     16can be used to check the differences between a tagged version and trunk,
     17or to review the set of differences between two branches.
    4418
    4519== InterWiki and InterTrac support ==
    4620
    47 An InterWiki link can be used for referring to a Wiki page located in another
    48 Wiki system, and by extension, to any object located in any other Web application,
    49 provided a simple URL mapping can be done.
     21An InterWiki link can be used to refer to a Wiki page located on another Wiki
     22system, and by extension, to any object located on any other Web site,
     23as long as simple URL mapping is possible.
    5024
    51 An InterTrac link can be seen as a scoped TracLinks. It is used for referring
    52 to a Trac resource (Wiki page, changeset, ticket, ...) located in another
    53 Trac environment. This makes it easier to work in a TracMultipleProjects setup,
    54 and seamlessly refer to resources from one Trac to another.
     25An InterTrac link can be used for referring  to a Trac resource (Wiki page,
     26changeset, ticket, ...) on an other Trac environment. This makes it easier to
     27work with multiple separate projects, and seamlessly refer to resources from
     28one Trac to another.
    5529
    56 == Use WSGI as web-frontend protocol ==
     30== Improved modularity ==
    5731
    58  ''Placeholder -- cmlenz, your take ;)''
     32Trac now supports database and version control backends as third-party plugins.
    5933
    60 == Better protection against spam ==
     34It is now easier to add support for new database backends. In addition to the
     35already existing support for SQLite and PostgreSQL, Trac now features
     36experimental support for the MySQL database.
    6137
    62 Trac now has in place the internal hooks necessary to filter out
    63 spam content. In order to take benefit from this, the SpamFilter
    64 plugin must be installed and enabled.
     38As for the version control systems, Trac still features best of breed Subversion
     39support, but the Subversion bindings and libraries are no longer mandatory
     40for using Trac itself. Other version control systems can be supported by
     41external plugins.
    6542
    66   ''We should probably package that plugin separately,
    67   but put it right beside the Trac packages, on the TracDownload page.''
     43== Improved notification system ==
     44
     45The encoding for emails sent out by Trac can now be confiured. This may
     46decrease email size and can avoid useless encoding for western languages
     47that make some touchy SMTP servers bounce the notifications.
     48
     49Support for local network installations using local email addresses
     50(addresses without a domain name) and a configurable default domain name
     51has been added, as well as support for both visible and blind carbon copies.
     52
     53== Support for spam protection ==
     54
     55Trac now provides extension point that allow plugins to intercept content
     56submissions, which can be used to filter out spam. One plugin that does
     57this is the SpamFilter plugin, which is available as a separate package:
     58
     59  http://trac.edgewall.org/wiki/SpamFilter
     60
     61This plugin implements a number of different strategies for testing content,
     62such as regular expression matching, IP blacklisting, and Akismet queries.
     63
     64== WSGI used as web server protocol ==
     65
     66Trac now uses WSGI (the "Python Web Server Gateway Interface") internally.
     67While Trac continues to provide builtin support for CGI, FastCGI and
     68mod_python, as well as the standalone server "tracd", you can now take
     69advantage of the WSGI support to use Trac in other setups, such as Twisted,
     70Paste, SCGI, or ISAPI.
    6871
    6972
     
    102105in which Unicode characters were represented using UTF-8
    103106encoding. This lead to various problems with most non-western
    104 languages. We now use the dedicated `unicode`
    105 datatype to consistently handle text written in any
    106 language.
    107 
    108 This removes all the problems caused by mistakenly cutting a UTF-8-encoded string between the bytes of a multi-byte character.
     107languages. We now use the dedicated `unicode`  datatype to
     108consistently handle text written in any language.
    109109
    110110=== Better way to programatically generate HTML fragments ===
    111111
    112 ''Placeholder: introduce briefly the Markup and Element classes''
     112Trac now provides utility code to programmatically generate HTML
     113snippets. This can be used in the various places where Trac expects
     114plugins to return small fragments of HTML bypassing the template
     115system. These utilities can be found in the trac.util.html module.
    113116
    114117=== Unit test framework for email notifications ===
    115118
    116 Email notifications can now be validated; unit tests include a private SMTP server
    117 and helper methods to extract and decode email data.
     119Email notifications can now be validated; unit tests include a private
     120SMTP server and helper methods to extract and decode email data.