bring back the explanation of our LGTM process
| ... | ... |
@@ -109,6 +109,18 @@ name and email address match your git configuration. The AUTHORS file is |
| 109 | 109 |
regenerated occasionally from the git commit history, so a mismatch may result |
| 110 | 110 |
in your changes being overwritten. |
| 111 | 111 |
|
| 112 |
+### Merge approval |
|
| 113 |
+ |
|
| 114 |
+Docker maintainers use LGTM (looks good to me) in comments on the code review |
|
| 115 |
+to indicate acceptance. |
|
| 116 |
+ |
|
| 117 |
+A change requires LGTMs from an absolute majority of the maintainers of each |
|
| 118 |
+component affected. For example, if a change affects docs/ and registry/, it |
|
| 119 |
+needs an absolute majority from the maintainers of docs/ AND, separately, an |
|
| 120 |
+absolute majority of the maintainers of registry |
|
| 121 |
+ |
|
| 122 |
+For more details see [MAINTAINERS.md](hack/MAINTAINERS.md) |
|
| 123 |
+ |
|
| 112 | 124 |
### Sign your work |
| 113 | 125 |
|
| 114 | 126 |
The sign-off is a simple line at the end of the explanation for the |