Changes between Version 31 and Version 32 of TracDev

Timestamp:

Oct 12, 2010, 10:28:50 PM (14 years ago)

Author:

Christian Boos

Comment:

improve presentation and wording

TracDev

@@ -1 +1 @@
 = Trac Development =
+
+{{{#!div style="float:right; margin-left: 4em; border-left: 2px solid #ccc; margin-bottom: 1em;"
+** Release Notes: [[TitleIndex(TracDev/ReleaseNotes/,hideprefix,format=compact)]] **
+
+** API changes: [[TitleIndex(TracDev/ApiChanges/,hideprefix,format=compact)]] **
+}}}
 
 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 
@@ -5 +11 @@
 version of Trac (currently 0.13dev). 
 
+
 We also do our best to signal what has been
 deprecated/removed between releases, see our [TracDev/ReleaseNotes Release Notes] and summary of [TracDev/ApiChanges API changes].
-Starting with 0.13dev, each ticket has an //API change// field, so we hopefully won't get any change get undocumented.
+
+
+Starting with 0.13dev, each ticket has an //API change// field, so we hopefully won't get any change remain undocumented.
 
 == How to get started?
@@ -13 +22 @@
 Start by doing a [TracDev/DevelopmentEnvironmentSetup Development Environment Setup] and become familiar with [TracInstall installing Trac] and creating new ["TracEnvironment"]s.
 
-Then, you should read a bit, in order to get familiar with Trac's [TracDev/ComponentArchitecture ComponentArchitecture], [TracDev/PluginDevelopment PluginDevelopment] and [TracDev/DatabaseApi DatabaseApi].
+Then, you should read a bit, in order to get familiar with Trac's [./ComponentArchitecture], [./PluginDevelopment] and [./DatabaseApi].
+The TracTroubleshooting page contains debugging tips which are also quite useful during development.  
 
-See also TracTroubleshooting, which contains useful debugging tips that are also quite useful during development.  There is also MostFrequentDuplicates which describes some of the most common issues encountered while running/debugging trac.
-
-Note that we're picky about our [TracDev/CodingStyle CodingStyle] and you'd better follow them when [TracDev/SubmittingPatches SubmittingPatches]. In order to be accepted, they should pass the [TracDev/UnitTests UnitTests] and the [TracDev/FunctionalTests FunctionalTests]. Ideally, you should also contribute new tests.
+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.
 
 Incidentally, discussions about Trac Development happen 
@@ -26 +34 @@
 (in the latter example, the "id" being the one of the ''Individual Message'').
 
-See TracDev/Branches and TracDev/Proposals as well as the TracDev/ToDo, for an overview of the open topics.
+See TracDev/Branches and TracDev/Proposals as well as the TracDev/ToDo, for an overview of the open topics (besides the [/roadmap], of course).
 
 == TracDev/ Index ==
-||= Release Notes =||= [TracDev/ApiChanges API changes] =||
-||[[TitleIndex(TracDev/ReleaseNotes/,hideprefix)]] || [[TitleIndex(TracDev/ApiChanges/,hideprefix)]] ||
 
 === Development Guides ===