Development Environment issues in Sep 2018
We plan to implement the following features:
-
how to add developers: See https://gitlab.com/AutowareAuto/AutowareAuto/wikis/Administration In summary:
- Contributors: are all set, this is a public project
- Developers: for approving merge requests and managing milestones users have to be added as project memebers
-
merging only over reviewed MRs; only masters can merge, i.e. are the reviewers: see link in the item above -
boards => setup a board with these stages: backlog, in progress, done https://gitlab.com/AutowareAuto/AutowareAuto/boards/775556 -
issue/MR templates: !1 (merged) -
art release script => so we can create a 0.1 release at the end of September and show a changelog --> #13 (closed)
-
"Documentation in form of Tutorials, Examples, How-Tos" => We will write an intro and would want that it gets rendered in pages -- infrastructure is done https://gitlab.com/AutowareAuto/AutowareAuto/merge_requests/2 -
integration tests (also including framework: custom from apex) => port and provide example with
apex_integration_tests
=> https://gitlab.com/AutowareAuto/AutowareAuto/issues/9 -
atom setup => if time allows - Debugging --> #14 (closed)
- Auto-completion --> #14 (closed)
- Auto-formatting --> #14 (closed)
-
Code navigation -
Go to declaration, go to definition
-
-
Building - Running --> #14 (closed)
-
Supporting multiple cmake
projects for use case of ROS 2 projects being all standalone cmake projects
What would then still be missing for later:
- arm --> #7 (closed)
- generation of debians --> #8 (closed)