... | ... | @@ -58,30 +58,13 @@ Improvements may be: |
|
|
|
|
|
Templates are usually available to help at the creation. However the following information **SHALL** be provided.
|
|
|
|
|
|
<ul type = "square">
|
|
|
<li>Short title</li>
|
|
|
<li>Add a proper description of the requested task</li>
|
|
|
<ul type = "disc">
|
|
|
<li>Indicate if the task is repository-wide</li>
|
|
|
</ul>
|
|
|
<li>Task <b>SHALL</b> be assigned</li>
|
|
|
<li>Labels <b>SHALL</b> be added:</li>
|
|
|
<ul type = "disc">
|
|
|
<li>At least the kind of improvement:</li>
|
|
|
<ul type = "circle">
|
|
|
<li>enhancement <img src="../images/enhancement-label.png" /></li>
|
|
|
<li>code cleanup</li>
|
|
|
</ul>
|
|
|
</ul>
|
|
|
</ul>
|
|
|
|
|
|
* Short title
|
|
|
* Add a proper description of the requested task
|
|
|
* Indicate if the task is repository-wide
|
|
|
* Task **SHALL** be assigned
|
|
|
* Labels **SHALL** be added:
|
|
|
* At least the kind of improvement:
|
|
|
* enhancement <img src="../images/enhancement-label.png" />
|
|
|
* <img src="../images/enhancement-label.png" />
|
|
|
* code cleanup
|
|
|
* If the improvement is not repository wide, indicate the functional part affected with a label
|
|
|
* create a new label if needed
|
... | ... | @@ -118,8 +101,8 @@ Templates are usually available to help at the creation. However the following i |
|
|
* Branch
|
|
|
* Commit ID
|
|
|
* Labels **SHALL** be added:
|
|
|
* Bug **SHALL** be present
|
|
|
* **NEW** label **SHALL** be set
|
|
|
* <img src="../images/bug-label.png" /> **SHALL** be present
|
|
|
* <img src="../images/new-label.png" /> label **SHALL** be set
|
|
|
* If the issue is located, indicate the functional part affected with a label
|
|
|
* create a new label if needed
|
|
|
* A **NEED-DATE SHALL** be added
|
... | ... | @@ -136,7 +119,7 @@ It will first assess if all the required information is present (as defined in t |
|
|
|
|
|
* The bug report does not have all the required labels.
|
|
|
* The bug report has insufficient information to act upon.
|
|
|
* The Technical Committee change the state label to 'NeedsInfo' in the issue report
|
|
|
* The Technical Committee change the state label to <img src="../images/needs-info-label.png" /> in the issue report
|
|
|
* If enough time passes and no new information is provided, the bug may be closed by default, as one of the No-Action states.
|
|
|
|
|
|
It will assess if the reported issue is valid. The reasons to decline an issue are (non-exclusive):
|
... | ... | @@ -152,23 +135,23 @@ It will assess if the reported issue is valid. The reasons to decline an issue a |
|
|
Once the issue is deemed valid by the Technical Committee, it shall assign someone to it.
|
|
|
|
|
|
* A dedicated fix branch is dedicated to the development as described in [Bug-fix branches](policy/branch#3-bug-fix-branches).
|
|
|
* The Technical Committee change the state label to 'Assigned' in the issue report
|
|
|
* The Technical Committee changes the state label to <img src="../images/assigned-label.png" /> in the issue report
|
|
|
|
|
|
## 3.3. Resolution of the issue ##
|
|
|
|
|
|
Once the assignee starts working on it, he/she **SHALL** change the state label to 'On-Going'.
|
|
|
Once the assignee starts working on it, he/she **SHALL** change the state label to <img src="../images/on-going-label.png" />.
|
|
|
|
|
|
Then the assignee implements a solution that should corresponds to one or several commits onto the `fix-XXXX-***` branch.
|
|
|
|
|
|
* The last commit message **SHALL** has the Issue ID as reference.
|
|
|
* The assignee **SHALL** change the state label to 'Fixed'.
|
|
|
* The assignee **SHALL** change the state label to <img src="../images/fixed-label.png" />.
|
|
|
* The assignee creates a Merge Request with the proper information.
|
|
|
|
|
|
By creating a Merge Request, the OAI Continuous Integration should be automatically triggered and provides a status within the merge request web interface. Emails could be also sent to assignee and integrators.
|
|
|
|
|
|
Based on the status, the Technical Committee decides to accept or not the Merge Request:
|
|
|
|
|
|
* The Technical Committee **SHALL** change the state label to 'Verified'.
|
|
|
* The Technical Committee **SHALL** change the state label to <img src="../images/verified-label.png" />.
|
|
|
* If OK, the merge request approval should start another CI job.
|
|
|
|
|
|
## 3.4. Closure of the issue ##
|
... | ... | |