Edgewall Software

Changes between Version 64 and Version 65 of TracDev


Ignore:
Timestamp:
Oct 17, 2015, 10:59:20 AM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes, removed link to deprecated page

Legend:

Unmodified
Added
Removed
Modified
  • TracDev

    v64 v65  
    99}}}
    1010
    11 These pages provide information about the development of Trac and its extensions, such as WikiMacros and other plugins.
     11These pages provide information about the development of Trac and its [th:HackIndex extensions].
    1212
    1313We 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.
     
    2020The TracTroubleshooting page contains some debugging tips which are also quite useful during development. 
    2121
    22 When 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.
     22When you're ready to contribute changes, note that we're picky about our [./CodingStyle] when [./SubmittingPatches]. For changes to be accepted, the modified Trac source should still pass the [./UnitTests] and the [./FunctionalTests]. Ideally, also contribute new tests.
    2323
    24 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, 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, use the wiki.
    2525
    26 You 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.
     26To refer to a mail from Trac-dev in this wiki, use the `googlegroups` InterWiki prefix, for example: googlegroups:trac-dev:1b9c4e3eaeda3a0d. You 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.
    2727
    2828== Development guides
     
    9090||= '''[./Branches Development Branches]''' =||
    9191{{{#!td style="vertical-align: top"
    92  // Blueprints for major changes on a topic //
     92Blueprints for major changes on a topic:
    9393[[TitleIndex(TracDev/Proposals/,hideprefix)]]
    9494
    9595}}}
    9696{{{#!td style="vertical-align: top"
    97  // Documentation for ongoing work in code branches //
     97Documentation for ongoing work in code branches:
    9898[[TitleIndex(TracDev/Branches/,hideprefix)]]
    9999