Changes between Version 14 and Version 15 of TracDev/ReleaseNotes/0.10
- Timestamp:
- Aug 26, 2006, 10:41:00 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev/ReleaseNotes/0.10
v14 v15 1 1 = 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 breed12 Subversion support, but the dependency on the Subversion bindings and13 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 useless21 encodings for western languages that make some touchy SMTP servers bounce22 the notifications.23 24 Improved support for local network installations supporting local email25 addresses (addresses without a domain name) and default domain name.26 27 Support for both visible and blind carbon copies.28 2 29 3 == Advanced diff support == … … 35 9 A related change is the possibility to navigate through a sequence 36 10 of ''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.11 of changes within a changeset inside a given directory. One can easily 12 start navigating such a sequence by following the new ''Last Change'' 13 navigation link present for the currently browsed path. 40 14 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...15 It's now also possible to compare two arbitrary paths at any revision. This 16 can be used to check the differences between a tagged version and trunk, 17 or to review the set of differences between two branches. 44 18 45 19 == InterWiki and InterTrac support == 46 20 47 An InterWiki link can be used for referring to a Wiki page located in another48 Wiki system, and by extension, to any object located in any other Web application, 49 provided a simple URL mapping can be done.21 An InterWiki link can be used to refer to a Wiki page located on another Wiki 22 system, and by extension, to any object located on any other Web site, 23 as long as simple URL mapping is possible. 50 24 51 An InterTrac link can be seen as a scoped TracLinks. It is used for referring52 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 fromone Trac to another.25 An InterTrac link can be used for referring to a Trac resource (Wiki page, 26 changeset, ticket, ...) on an other Trac environment. This makes it easier to 27 work with multiple separate projects, and seamlessly refer to resources from 28 one Trac to another. 55 29 56 == Use WSGI as web-frontend protocol==30 == Improved modularity == 57 31 58 ''Placeholder -- cmlenz, your take ;)'' 32 Trac now supports database and version control backends as third-party plugins. 59 33 60 == Better protection against spam == 34 It is now easier to add support for new database backends. In addition to the 35 already existing support for SQLite and PostgreSQL, Trac now features 36 experimental support for the MySQL database. 61 37 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. 38 As for the version control systems, Trac still features best of breed Subversion 39 support, but the Subversion bindings and libraries are no longer mandatory 40 for using Trac itself. Other version control systems can be supported by 41 external plugins. 65 42 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 45 The encoding for emails sent out by Trac can now be confiured. This may 46 decrease email size and can avoid useless encoding for western languages 47 that make some touchy SMTP servers bounce the notifications. 48 49 Support for local network installations using local email addresses 50 (addresses without a domain name) and a configurable default domain name 51 has been added, as well as support for both visible and blind carbon copies. 52 53 == Support for spam protection == 54 55 Trac now provides extension point that allow plugins to intercept content 56 submissions, which can be used to filter out spam. One plugin that does 57 this is the SpamFilter plugin, which is available as a separate package: 58 59 http://trac.edgewall.org/wiki/SpamFilter 60 61 This plugin implements a number of different strategies for testing content, 62 such as regular expression matching, IP blacklisting, and Akismet queries. 63 64 == WSGI used as web server protocol == 65 66 Trac now uses WSGI (the "Python Web Server Gateway Interface") internally. 67 While Trac continues to provide builtin support for CGI, FastCGI and 68 mod_python, as well as the standalone server "tracd", you can now take 69 advantage of the WSGI support to use Trac in other setups, such as Twisted, 70 Paste, SCGI, or ISAPI. 68 71 69 72 … … 102 105 in which Unicode characters were represented using UTF-8 103 106 encoding. 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. 107 languages. We now use the dedicated `unicode` datatype to 108 consistently handle text written in any language. 109 109 110 110 === Better way to programatically generate HTML fragments === 111 111 112 ''Placeholder: introduce briefly the Markup and Element classes'' 112 Trac now provides utility code to programmatically generate HTML 113 snippets. This can be used in the various places where Trac expects 114 plugins to return small fragments of HTML bypassing the template 115 system. These utilities can be found in the trac.util.html module. 113 116 114 117 === Unit test framework for email notifications === 115 118 116 Email notifications can now be validated; unit tests include a private SMTP server117 and helper methods to extract and decode email data.119 Email notifications can now be validated; unit tests include a private 120 SMTP server and helper methods to extract and decode email data.