From 7a85cf09f4c5282842698247e8065d6761ed7dfb Mon Sep 17 00:00:00 2001 From: Tobias Reiher Date: Fri, 16 Feb 2024 15:03:39 +0100 Subject: [PATCH] Update development guide Ref. None --- doc/development_guide/index.rst | 15 +-------------- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/doc/development_guide/index.rst b/doc/development_guide/index.rst index 29f1c6e3d..14bf3f52f 100644 --- a/doc/development_guide/index.rst +++ b/doc/development_guide/index.rst @@ -8,7 +8,7 @@ Setup Additionally to the dependencies listed in the `User's Guide `_ the following software is required: - `AUnit `_ (if FSF GNAT is used) -- `Dnsmasq `_ +- `Dnsmasq `_ (to test an example app) - `Node.js `_ 20.5.0 or higher (see `nvm `_ for an alternative installation method) - `TeX Live `_ (to create the PDF documentation) @@ -177,16 +177,3 @@ All review comments must be set to resolved by a reviewer before a pull request Force pushing is required and accepted for rebasing to the base branch. Commits may be squashed before the pull request is merged to prevent a high number of "Fix review comments" commits. Squashing should be avoided before the changes have been accepted by all reviewers. - -Project management -================== - -The work is organized and prioritized using GitHub's project boards. -At any time there is at least one project board for the planned next release and a project board for all potential future tasks. -A project board for an upcoming release has four columns: - -- To Do: Non-processed issues planned for the release. -- Design: Issues for which the design is currently created or discussed. Assigned to a specific person. Skipped for small issues or bugs. -- Implementation: Issues which are currently implemented. Assigned to a specific person. -- Review: Completed issues for which a PR is open or will be opened soon. Each issue is linked to the corresponding PR. -- Done: Closed issues.