Слияние кода завершено, страница обновится автоматически
Contents:
Definition: An issue refers to a task to be completed. Such task can be a "problem", "transaction", "requirement", or "suggestion". Each issue should contain all the information and history of the task, so that other viewers can understand all the aspects and processes of the task.
Source and function: The concept of issue originates from the customer service department. When a user makes a call to report a problem, the customer service personnel create a ticket. Each subsequent processing step and each communication with the user need to be updated to the ticket to record all process information. This is the predecessor of the issue. As it expands, the issue evolves into a full-function project management tool for developing and executing software development plans.
The openEuler community uses the issue tracking and management system provided by Gitee.
Only the current repository can be viewed and operated on the Issue panel. Gitee also provides the global view of issues.
Global view of the organization: Click the Issues panel of the openEuler organization to view all issues of the organization.
Individual global view: Click any issue in the organization global view. The individual workspace page is displayed. Click Task on the left to view and operate all issues related to you. You can select either of the two display modes. You can also filter, filter, and sort data based on different conditions on the toolbar.
For details about the complete requirement issue handling process, see the following flowchart.
Step 1. Create a requirement issue. (Issue status: Backlog)
Go to the repository of the team or project corresponding to the requirement. For details about how to find the repository, see this section. On the Issues panel, click +New Issue.
If you are not sure about the team or project corresponding to the requirement, create an issue in the community repository. The community developers will help you find the team or project.
Select Requirement in the issue type drop-down list next to the title box. The requirement issue template is displayed.
Briefly describe the key points of the requirement in the title.
Describe the scenario and value of the requirement in the description.
Note: Clear and complete description helps group members understand and accept the requirement, and schedule the development plan more quickly.
Step 2. Team members review the issue. (Issue statuses: Doing - accepted, Backlog - additional information needed, Declined - rejected)
Step 2.1: Accept after review
If a reviewer (maintainer or committer) thinks that the requirement can be accepted, the reviewer needs to supplement information about the accepted requirement, including:
Step 2.2: Suspend due to unclear description
If team members think that the issue description is not clear, they can leave a message in the comment area or discuss the issue in the mailing list, and ask the submitter to supplement related information.
Step 2.3: Reject after review
If a team member rejects a requirement because it is of low value or for other reasons, the team member can leave a message in the comment area or discuss the reasons in the mailing list. After confirming the rejection, change the status of the issue to Declined. (Go to Step 4)
Step 3. Claim or assign an issue. (Issue status: Open)
Requirements in the development phase can be claimed proactively or assigned by team members. You can enter /assign in the comment area to assign the issue to yourself or others.
Step 4. Close the issue. An issue can be closed when:
Discovering and submitting issues is one of the good ways to contribute to the community. This section describes how to write a well-crafted issue.
Step 1. Create a bug issue.
[Environment]
Hardware Information
- Provide information about the hardware in the bare device scenario.
- Provide the XML file or configuration information of the VM in the VM scenario.
Software Information
- OS version and branch
- Kernel
- Version of the bug component
Network Information
- Provide network topology information in special networking.
[Bug Reproduction Procedure]: Describe the detailed operation procedure.
[Actual Result]: Describe the result and impact of the bug.
[Attachments]
System message logs, component logs, dump information, and images.
Step 2: Review the bug.
Step 3: Claim or assign an issue. Issues can be claimed proactively or assigned by team members. You can enter /assign in the comment area to assign the issue to yourself or others.
Step 4: Modify the code and submit a PR. After modifying and locally verifying the code, attach the link to the issue when submitting a PR. For details, see Associate a Commit to an Issue in the Gitee help document. For details about how to submit a PR, see the Pull Request Submission Guide.
Step 5: Verify the modification in the project. Verify the PR within the project. If the verification fails, go back to Step 4. If the verification is passed and the issue is not related to the openEuler version, close the issue as a project team issue.
Step 6: Submit or release a patch. The maintainer of the project team determines the way to address the issue, including updating the software package and releasing a patch. If the issue is a key issue related to the openEuler version, it is then verified by the QA team.
Step 7: Wait for the QA team to verify the issue at the version level. After the verification is successful, proceed to Step 8.
Step 8: Close the issue. Specify the reason for closing the issue in the description. The reasons include:
If the description and reproduction procedure you submitted with the issue are clear and the bug can be located, a participant will directly locate and fix the bug. However, the developer who is responsible for tracking this issue may need more information from you. Your cooperation will be appreciated.
For details about how to handle security issues, see this document.
Вы можете оставить комментарий после Вход в систему
Неприемлемый контент может быть отображен здесь и не будет показан на странице. Вы можете проверить и изменить его с помощью соответствующей функции редактирования.
Если вы подтверждаете, что содержание не содержит непристойной лексики/перенаправления на рекламу/насилия/вульгарной порнографии/нарушений/пиратства/ложного/незначительного или незаконного контента, связанного с национальными законами и предписаниями, вы можете нажать «Отправить» для подачи апелляции, и мы обработаем ее как можно скорее.
Опубликовать ( 0 )