|
Size: 694
Comment:
|
← Revision 61 as of 2024-03-15 12:14:37 ⇥
Size: 1903
Comment: Remove outdated comment on Python version. See README.md and the Requirements wiki page instead.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * [[/Workflow]]: our Mercurial workflow * [[/C++Code]]: coding conventions and style guide for C++ code * [[/C++Whitespace]]: how to indent, where to break lines, where to put spaces etc. * [[/Uncrustify]]: using the uncrustify source code pretty printer, including integration with Mercurial |
* [[/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 * [[/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 * [[/GithubActions]]: information on Github actions * [[/ImplementationDetails]]: more in-depth descriptions on how some classes are implemented * [[/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 * [[/CMake]]: Usage of CMake (custom builds, tips and tricks) * [[/Profiling]]: on using valgrind and friends * [[/ReleaseWorkflow]]: how to create a release version * [[/ChangelogFormat]]: description of the changelog format * [[/Sprint]]: information, statistics, and news about our Fast Downward sprints * [[/Blog]]: articles describing parts of the code base |
| Line 14: | Line 29: |
| * '''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/ |
|
| Line 15: | Line 32: |
| * '''Commit messages:''' The first line of the commit message should consist of a self-contained summary and be no longer than '''67 characters'''. All other lines should be below '''80 characters'''. |
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
/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
/GithubActions: information on Github actions
/ImplementationDetails: more in-depth descriptions on how some classes are implemented
/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
/CMake: Usage of CMake (custom builds, tips and tricks)
/Profiling: on using valgrind and friends
/ReleaseWorkflow: how to create a release version
/ChangelogFormat: description of the changelog format
/Sprint: information, statistics, and news about our Fast Downward sprints
/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.