Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Eclipse Projects
Oniro Core
docs
Merge requests
!9
Add common nomenclature for new issue
Code
Review changes
Check out branch
Download
Patches
Plain diff
Open
Add common nomenclature for new issue
lucafavaretto/docs:nomenclature
into
main
Overview
20
Commits
1
Pipelines
4
Changes
1
Open
Luca Favaretto
requested to merge
lucafavaretto/docs:nomenclature
into
main
2 years ago
Overview
20
Commits
1
Pipelines
4
Changes
1
Expand
Signed-off-by: Luca Favaretto
luca.favaretto@kalpa.it
Closed:
oniro#590
0
0
Merge request reports
Compare
main
version 2
2164c426
2 years ago
version 1
8d2fd29e
2 years ago
main (HEAD)
and
latest version
latest version
94fbe7f0
1 commit,
2 years ago
version 2
2164c426
1 commit,
2 years ago
version 1
8d2fd29e
1 commit,
2 years ago
1 file
+
76
−
1
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
contributing/bug_policy.rst
+
76
−
1
Options
@@ -7,6 +7,9 @@
Bug Handling Process
####################
.. contents::
:depth: 3
Overview
********
@@ -20,7 +23,79 @@ How to Report a Bug?
If you think you have found a bug in our distribution, please file a bug report
in our bug tracker and in the project that you think is the source of the
issue. Use the provided template:
issue.
Nomenclature for a new issue
^^^^^^^^^^^^^^^^^^^^^^^^^^^
In |main_project_name|, for the opening of a new `Issue::Bug` the team decided to adopt
a common nomenclature to apply to the title of each new issue.
Depending on the scope to which the issue refers, three options are defined.
Option 1 - Board-related
------------------------
When the issue is opened related to a specific board, the parameters to be given
are: **Domain** and **Board**.
| [MAINTENANCE][$BOARD] - $Title
| [NETWORK][$BOARD] - $Title
| [OpenHarmony][$BOARD] - $Title
| [OTA][$BOARD] - $Title
| [SECURITY][$BOARD] - $Title
| [PERFORMANCE][$BOARD] - $Title
| [HW][$BOARD] - $Title
| [TOOLCHAIN][$BOARD] - $Title
| [MISC][$BOARD] - $Title
*Example:*
[Maintenance][BOARD X] - Build failed due to ModemManager error
Option 2 - Blueprint related
----------------------------
When the issue is opened related to a specific blueprint, the parameters to be given
are: **Blueprint** and **Domain**; if necessary even **Board** (when Blueprint has
more than one board in the configuration. To be omitted if there is only one board).
| [$BP - MAINTENANCE][$BOARD] - $Title
| [$BP - NETWORK][$BOARD] - $Title
| [$BP - OpenHarmony][$BOARD] - $Title
| [$BP - OTA][$BOARD] - $Title
| [$BP - SECURITY][$BOARD] - $Title
| [$BP - PERFORMANCE][$BOARD] - $Title
| [$BP - HW][$BOARD] - $Title
| [$BP - TOOLCHAIN][$BOARD] - $Title
| [$BP - MISC][$BOARD] - $Title
*Examples:*
| [CATS - HW] - Black screen when flashing the image
| [ENERGY GATEWAY - OTA][Raspberry Pi 4B] - Can't upload the image via OTA
Option 3 - Domain related
-------------------------
When the issue isn't related to a specific blueprint or board, the parameters
to be given is **Domain**.
| [MAINTENANCE] - $Title
| [NETWORK] - $Title
| [OpenHarmony] - $Title
| [OTA] - $Title
| [SECURITY] - $Title
| [PERFORMANCE] - $Title
| [HW] - $Title
| [TOOLCHAIN] - $Title
| [MISC] - $Title
*Example:*
[SECURITY] - Security configuration error on Linux Kernel
Bug template
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To fill the information of the issue use the provided template:
* The module affected
* What is the action to reproduce the bug? (Steps to reproduce)
Loading