Edgewall Software

Changes between Version 61 and Version 62 of TracDev


Ignore:
Timestamp:
Jul 27, 2015, 9:01:36 PM (9 years ago)
Author:
figaro
Comment:

Start of a rationalisation

Legend:

Unmodified
Added
Removed
Modified
  • TracDev

    v61 v62  
    99}}}
    1010
    11 These pages provide information about the development of Trac and its extensions, such as WikiMacros and other plugins. Most of the information was originally written for Trac 0.9, but we try to maintain it up-to-date with the latest versions, currently Trac 1.0dev.
     11These pages provide information about the development of Trac and its extensions, such as WikiMacros and other plugins.
    1212
    1313We 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].
     
    1616== How to get started?
    1717
    18 Start by doing a [TracDev/DevelopmentEnvironmentSetup Development Environment Setup] and become familiar with [TracInstall installing Trac] and creating new ["TracEnvironment"]s.
     18Start by setting up a [TracDev/DevelopmentEnvironmentSetup Development Environment] and become familiar with [TracInstall installing Trac] and creating new ["TracEnvironment"]s.
    1919
    20 Then, you should read a bit to get familiar with Trac's [./ComponentArchitecture], [./PluginDevelopment] and [./DatabaseApi].
     20Then, you should get familiar with Trac's [./ComponentArchitecture], [./PluginDevelopment] and [./DatabaseApi].
    2121The TracTroubleshooting page contains some debugging tips which are also quite useful during development. 
    2222
    23 When you're ready to start hacking the code, make some modifications, see what happens and 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 it when [./SubmittingPatches]. In order to be accepted, the modified Trac source should still pass the [./UnitTests] and the [./FunctionalTests]. Ideally, also contribute new tests.
     23When 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.
    2424
    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
    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.
     25Discussions 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.
     26
     27You 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.
    2728
    2829== Development guides
     
    4041 - **[./SubmittingPatches]**
    4142 - [./DevelopmentWorkflow]
    42  - [./ReleaseChecklist] and [./ReleaseTesting]
     43 - [./ReleaseChecklist]
    4344 - [./ToDo]
    4445 - [wiki:TracTicketTriage]
     
    104105}}}
    105106|--------------------------------------
    106 ||= '''Scratch Pad''' =|| \
    107 ||= '''Ideas''' =||
    108 ||||  //Group enhancement ideas related to a same component or functional area//  ||
     107||= '''Scratch Pad''' for developers =|| \
     108||= '''Ideas''' from users  =||
    109109{{{#!td style="vertical-align: top"
    110   // -- from the point of view of the developers // 
    111110[[TitleIndex(TracDev/ScratchPad/,hideprefix)]]
    112111}}}
    113112{{{#!td style="vertical-align: top"
    114   // -- with the user's hat on // 
    115113[[TitleIndex(TracIdeas/,hideprefix)]]
    116114}}}