| 9 | | These pages provide information about the development of Trac and extensions for Trac (such as WikiMacros and other kinds of plugins). Most of the information |
| 10 | | was written for 0.9, but we try to maintain it up-to-date with the latest |
| 11 | | version of Trac (currently 0.13dev). |
| | 9 | These pages provide information about the development of Trac and its extensions, such as WikiMacros and other kinds of plugins. Most of the information |
| | 10 | was originally written for Trac 0.9, but we try to maintain it up-to-date with the latest |
| | 11 | versions (currently Trac 0.13dev). |
| 14 | | We also do our best to signal what has been |
| 15 | | deprecated/removed between releases, see our [TracDev/ReleaseNotes Release Notes] and summary of [TracDev/ApiChanges API changes]. |
| 16 | | |
| 17 | | |
| 18 | | Starting with 0.13dev, each ticket has an //API change// field, so we hopefully won't get any change remain undocumented. |
| | 14 | We also do our best to keep track of what has been |
| | 15 | deprecated/removed between releases, see our [TracDev/ReleaseNotes Release Notes] and the summary of [TracDev/ApiChanges API Changes]. |
| | 16 | Starting with 0.13dev, each ticket has an //API change// field, which hopefully will make it easier to cover every changes. |
| 27 | | When you're ready hacking the code, make some modifications, see what happens, experiment. When you're about to make real changes that you want to contribute back, note that we're picky about our [./CodingStyle] and you'd better follow them when [./SubmittingPatches]. In order to be accepted, they should pass the [./UnitTests] and the [./FunctionalTests]. Ideally, you should also contribute new tests. |
| | 25 | When you're ready hacking the code, make some modifications, see what happens, experiment. When you're about to make real changes that you want to contribute back, note that we're picky about our **[./CodingStyle]** and you'd better follow them when [./SubmittingPatches]. In order to be accepted, they should pass the [./UnitTests] and the [./FunctionalTests]. Ideally, you should also contribute new tests. |
| 30 | | on the [http://groups.google.com/group/trac-dev/topics Trac-Dev] |
| 31 | | mailing list. `Trac-Dev` can also be used as an InterWiki prefix |
| 32 | | in order to refer to specific mails sent to that MailingList, |
| 33 | | e.g. Trac-Dev:1, or googlegroups:trac-dev:1b9c4e3eaeda3a0d |
| 34 | | (in the latter example, the "id" being the one of the ''Individual Message''). |
| 35 | | |
| 36 | | See TracDev/Branches and TracDev/Proposals as well as the TracDev/ToDo, for an overview of the open topics (besides the [/roadmap], of course). |
| | 28 | on the [http://groups.google.com/group/trac-dev/topics Trac-dev] |
| | 29 | 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, be sure to have searched the archive first, in order to avoid rehashing old discussions. For longer term developments, or for documentation purpose, 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 |
| | 30 | (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). |
