Edgewall Software

Changes between Version 62 and Version 63 of TracDev


Ignore:
Timestamp:
Aug 1, 2015, 11:30:53 AM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TracDev

    v62 v63  
    44** Release Notes: [[TitleIndex(TracDev/ReleaseNotes/,hideprefix,format=compact)]] ** \\
    55** API Changes: [[TitleIndex(TracDev/ApiChanges/,hideprefix,format=compact)]] ** \\
    6 ** API Doc:  [http://www.edgewall.org/docs/tags-trac-0.11.7/epydoc/ 0.11], [http://www.edgewall.org/docs/branches-0.12-stable/epydoc/ 0.12],
     6** API Doc: [http://www.edgewall.org/docs/tags-trac-0.11.7/epydoc/ 0.11], [http://www.edgewall.org/docs/branches-0.12-stable/epydoc/ 0.12],
    77[http://www.edgewall.org/docs/branches-1.0-stable/html/ 1.0],
    88[http://www.edgewall.org/docs/trac-trunk/html/ 1.1] ^[#see-ApiDocs (*)]^
    … …  
    1111These pages provide information about the development of Trac and its extensions, such as WikiMacros and other plugins.
    1212
    13 We also keep track of what has been deprecated/removed between releases, see our [TracDev/ReleaseNotes Release Notes] and the summary of [TracDev/ApiChanges API Changes].
    14 Starting with 1.0dev, each ticket has an //API change// field, which will make it easier to cover every change.
     13We also keep track of what has been deprecated or removed between releases, see our [TracDev/ReleaseNotes Release Notes] and the summary of [TracDev/ApiChanges API Changes]. API Changes are summarised using the ''API change'' field attached to every ticket; this is a feature implemented since 1.0dev.
    1514
    1615== How to get started?
    … …  
    2322When you're ready to make changes that you want to contribute, note that we're picky about our [./CodingStyle] when [./SubmittingPatches]. To be accepted, the modified Trac source should still pass the [./UnitTests] and the [./FunctionalTests]. Ideally, also contribute new tests.
    2423
    25 Discussions about Trac Development happen on the [http://groups.google.com/group/trac-dev/topics Trac-dev] mailing list. New development ideas are usually best discussed first on that list, it's a quick and easy way to get feedback on any given topic or question. As usual, search the archive first, in order to avoid rehashing old discussions. For longer term developments, or for documentation purposes, one should rather use the wiki. For referring to a mail from Trac-dev in this wiki, use the `googlegroups` InterWiki prefix e.g. googlegroups:trac-dev:1b9c4e3eaeda3a0d.
     24Discussions about Trac Development happen on the [http://groups.google.com/group/trac-dev/topics Trac-dev] mailing list. New development ideas are usually best discussed first on that list, it's a quick and easy way to get feedback on any given topic or question. As usual, search the archive first, to avoid rehashing old discussions. For longer term developments, or for documentation purposes, one should rather use the wiki. For referring to a mail from Trac-dev in this wiki, use the `googlegroups` InterWiki prefix e.g. googlegroups:trac-dev:1b9c4e3eaeda3a0d.
    2625
    2726You can see the message identifier  in the address bar of your browser when viewing the message in Individual Message view mode. You can go there from the default threaded view by clicking on //More options// and then on the //Individual Message// or //Show Original// links.
    … …  
    10099
    101100See also:
    102  - [https://github.com/edgewall/trac/network forks on github]
    103  - [https://bitbucket.org/edgewall/trac/descendants forks on bitbucket]
     101 - [https://github.com/edgewall/trac/network Forks on Github]
     102 - [https://bitbucket.org/edgewall/trac/descendants Forks on Bitbucket]
    104103 - [wiki:TracTeam/Repositories Developer repositories]
    105104}}}