Changes between Version 64 and Version 65 of TracDev
- Timestamp:
- Oct 17, 2015, 10:59:20 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracDev
v64 v65 9 9 }}} 10 10 11 These pages provide information about the development of Trac and its extensions, such as WikiMacros and other plugins.11 These pages provide information about the development of Trac and its [th:HackIndex extensions]. 12 12 13 13 We 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. … … 20 20 The TracTroubleshooting page contains some debugging tips which are also quite useful during development. 21 21 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.22 When 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. 23 23 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.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, use the wiki. 25 25 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.26 To 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. 27 27 28 28 == Development guides … … 90 90 ||= '''[./Branches Development Branches]''' =|| 91 91 {{{#!td style="vertical-align: top" 92 // Blueprints for major changes on a topic // 92 Blueprints for major changes on a topic: 93 93 [[TitleIndex(TracDev/Proposals/,hideprefix)]] 94 94 95 95 }}} 96 96 {{{#!td style="vertical-align: top" 97 // Documentation for ongoing work in code branches // 97 Documentation for ongoing work in code branches: 98 98 [[TitleIndex(TracDev/Branches/,hideprefix)]] 99 99