Information for developers#

Subpages#

Blog: articles describing parts of the code base
Changelog format: description of the changelog format
CMake: Usage of CMake (custom builds, tips and tricks)
Code review: how to use Github pull requests for code reviews
Coding conventions: coding conventions for C++ code
Development setup: which tools to install for working on the planner
Git: our Git workflow and Git tips and tricks
Github actions: information on Github actions
Implementation details: more in-depth descriptions on how some classes are implemented
Long term plans: long-term wishlist of changes with broader scope
Problem Transformations: problem transformations performed by the planner that might trip up users interested in non-classical planning
Profiling: on using valgrind and friends
Release workflow: how to create a release version
Requirements: the set of rules regarding which versions of operating systems, compilers etc. we support
Sprint: information, statistics, and news about our Fast Downward sprints
Style conventions: style conventions for C++ code and clang-format configuration
Translator Output Format v4: ideas for a future translator output format.

Mailing lists: Core developers, please subscribe to both the public and the internal mailing lists mentioned on the home page.
Admin interface to the internal mailing list: https://www.maillist.unibas.ch/mailman/options/downward-dev/
Python code: We follow PEP 8.