| 1 |
On Sun, 29 Jul 2018 00:40:18 +0300 |
| 2 |
Mikle Kolyada <zlogene@g.o> wrote: |
| 3 |
|
| 4 |
> Hello, |
| 5 |
> |
| 6 |
> The Gentoo QA team would like to introduce the following policy that |
| 7 |
> would be applied to individuals breaking the state and quality of the |
| 8 |
> main gentoo.git tree |
| 9 |
> |
| 10 |
> ( as we do not have this strictly documented yet): |
| 11 |
> |
| 12 |
> <policy> |
| 13 |
> |
| 14 |
> If recommended |
| 15 |
|
| 16 |
It's not called "recommended" but "enforced". |
| 17 |
|
| 18 |
> Gentoo workflow policies are not followed by an |
| 19 |
> individual developer |
| 20 |
> (e.g make major changes to the widely used eclasses without prior |
| 21 |
> discussion on the mailing list or |
| 22 |
> commit changes that lead to multiple CI checks failure) |
| 23 |
|
| 24 |
Here should go exhaustive list of links to the policies to be enforced. |
| 25 |
|
| 26 |
> the standard QA |
| 27 |
> procedure is: |
| 28 |
> |
| 29 |
> 1.) Two warnings granted by QA team, after two independent breakages |
| 30 |
> 2.) Revoking the commit access for 14 days |
| 31 |
> |
| 32 |
> These violations will be evaluated individually by all QA team members. |
| 33 |
> Warnings can be revoked, if during 6 months period a developer makes at |
| 34 |
> least 20 non trivial changes not producing more breakages. |
| 35 |
> |
| 36 |
> </policy> |
| 37 |
|
| 38 |
-- |
| 39 |
|
| 40 |
Sergei |
Archives