Issues management
Issues are managed in built-in issues tracking system.
Issues labels categorized and explained:
- type - each issue shall have at least one label from this group assigned:
- bug - reports malfunction of the product which is unrelated to security (how to report security issues)
- enhancement - feature request for code improvement
- documentation - feature request for documentation improvement
- question - user question
- bus impact - labels group used to mark issues related to certain bus types:
- CAN - related to CAN specific implementation or characterstic
- LIN - related to CAN specific implementation or characterstic
- Ethernet - related to Ethernet specific implementation or characterstic
- FlexRay - related to FlexRay specific implementation or characterstic
- K-Line - related to K-Line specific implementation or characterstic
- closure reason - use labels from these group to mark issues that are closed without resolution:
- duplicate - another simlar issue is already created
- invalid - either not enough information is provided (even after a request for clarification) or it is unrelated to this product
- wontfix - even though we accept that the issue is valid, we decide to acknowledge the risk and consciously ignore it
- others:
- dependecies - issues created by dependabot
- help wanted - use it if you are assigned to a issue, but you kinda stack or you do not know what to do next
Each milestone is meant to describe one major release. It must contain description what is the intention of the release and what value does it carry.
Development project is used to track progress and current status of the stories. On the picture below, you can see the workflow of the isssues. It is rather intuitive, but if you have any doubts, you would probably find missing information in Software Development Life Cycle article.
