|
Size: 1337
Comment:
|
Size: 2037
Comment: add linkn to requirements
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * [[/Mercurial]]: our Mercurial workflow and Mercurial tips and tricks | * [[/Requirements]]: the set of rules regarding which versions of operating systems, compilers etc. we support * [[/DevelopmentSetup]]: which tools to install for working on the planner * [[/AddingSourceFiles]]: how to add new source files to the planner * [[/Git]]: our Git workflow and Git tips and tricks |
| Line 10: | Line 13: |
| * [[/Uncrustify]]: using the {{{uncrustify}}} source code pretty printer, including integration with Mercurial * [[/CodeReview]]: how to use the Rietveld code review tool with our codebase * [[/GkiGrid]]: how to run experiments on the GKI grid |
* [[/Uncrustify]]: using the {{{uncrustify}}} source code pretty printer * [[/Includes]]: using {{{include-what-you-use}}} to find missing/redundant includes and forward declarations * [[/CodeReview]]: how to use Github pull requests for code reviews |
| Line 14: | Line 17: |
| * [[/GithubActions]]: information on Github actions | |
| Line 16: | Line 20: |
| * [[/ReviewQueue]]: Malte's FIFO list of issues to review * [[/LongTermPlans]]: long-term wishlist of changes with broader scope |
|
| Line 17: | Line 23: |
| * [[/CmakeTipsAndTricks]]: tips and tricks for CMake * [[/Profiling]]: on using valgrind and friends * [[/ReleaseWorkflow]]: how to create a release version * [[/ChangelogFormat]]: description of the changelog format * [[/Blog]]: articles describing parts of the code base |
|
| Line 21: | Line 32: |
| * '''Admin interface to the internal mailing list:''' https://lists.informatik.uni-freiburg.de/mailman/admin/downward-dev * '''Python code:''' We follow [[http://www.python.org/dev/peps/pep-0008/|PEP 8]] and support Python 2.7 and Python >= 3.2. |
* '''Admin interface to the internal mailing list:''' https://www.maillist.unibas.ch/mailman/options/downward-dev/ * '''Python code:''' We follow [[http://www.python.org/dev/peps/pep-0008/|PEP 8]] and support Python >= 3.6. |
Back to the HomePage.
Information for developers
Subpages:
/Requirements: the set of rules regarding which versions of operating systems, compilers etc. we support
/DevelopmentSetup: which tools to install for working on the planner
/AddingSourceFiles: how to add new source files to the planner
/Git: our Git workflow and Git tips and tricks
/CodingConventions: coding conventions for C++ code
/Whitespace: how to indent, where to break lines, where to put spaces etc. in C++ code
/Uncrustify: using the uncrustify source code pretty printer
/Includes: using include-what-you-use to find missing/redundant includes and forward declarations
/CodeReview: how to use Github pull requests for code reviews
/BuildBot: buildbot information
/GithubActions: information on Github actions
/ImplementationDetails: more in-depth descriptions on how some classes are implemented
/CodeBasesToMerge: code from papers we want to merge in the (medium-term) future
/ReviewQueue: Malte's FIFO list of issues to review
/LongTermPlans: long-term wishlist of changes with broader scope
/ProblemTransformations: problem transformations performed by the planner that might trip up users interested in non-classical planning
/CmakeTipsAndTricks: tips and tricks for CMake
/Profiling: on using valgrind and friends
/ReleaseWorkflow: how to create a release version
/ChangelogFormat: description of the changelog format
/Blog: articles describing parts of the code base
Other bits and pieces
Mailing lists: Core developers, please subscribe to both the public and the internal mailing lists mentioned on the HomePage.
Admin interface to the internal mailing list: https://www.maillist.unibas.ch/mailman/options/downward-dev/
Python code: We follow PEP 8 and support Python >= 3.6.