Line 123: |
Line 123: |
| | | |
| a. The user finds a bug in the latest release and then puts it into track. | | a. The user finds a bug in the latest release and then puts it into track. |
| + | |
| b. The bugsquad does triage. Triage means assessing the bug, | | b. The bugsquad does triage. Triage means assessing the bug, |
| validating it, and giving it a priority, and milestone (which release | | validating it, and giving it a priority, and milestone (which release |
| its going to be fixed in.) | | its going to be fixed in.) |
| + | |
| c. At some time, someone will try to fix it, usually a core developer. | | c. At some time, someone will try to fix it, usually a core developer. |
| If it’s not a core developer, it will always be attached as a patch | | If it’s not a core developer, it will always be attached as a patch |
| and reviewed. | | and reviewed. |
| + | |
| d. Next step is peer review. | | d. Next step is peer review. |
| + | |
| e. Patch gets improved, turned down, or accepted. This loop will | | e. Patch gets improved, turned down, or accepted. This loop will |
| continue until the parties are happy with the code status. | | continue until the parties are happy with the code status. |
| + | |
| f. Someone with commit access commits the patch. | | f. Someone with commit access commits the patch. |
| | | |