| 1 |
On 11/17/2016 02:16 AM, Michael Palimaka wrote: |
| 2 |
> |
| 3 |
> # strict - have portage react strongly to conditions that have the |
| 4 |
> potential to be dangerous |
| 5 |
> ... |
| 6 |
> FEATURES="collision-protect ipc-sandbox network-sandbox sandbox |
| 7 |
> split-log split-elog strict test userfetch userpriv usersandbox" |
| 8 |
|
| 9 |
Maybe "stricter" too if it's not absent on purpose. |
| 10 |
|
| 11 |
|
| 12 |
> * A leaf package such as {{package|kde-apps/kcalc}} may not require any |
| 13 |
> runtime testing at all |
| 14 |
|
| 15 |
For packages that have a small number of users, this might miss the fact |
| 16 |
that a package e.g. segfaults immediately. Maintainers can't always test |
| 17 |
on every architecture, and if there's only three ~ppc (say) users, then |
| 18 |
they may miss the 30 day window. |
| 19 |
|
| 20 |
|
| 21 |
> === amd64 === |
| 22 |
> * Any developer may perform {{keyword|amd64}} stabilisations - it is not |
| 23 |
> necessary to be on the arch team |
| 24 |
> |
| 25 |
> === x86 === |
| 26 |
> * Any developer may perform {{keyword|x86}} stabilisations - it is not |
| 27 |
> necessary to be on the arch team |
| 28 |
|
| 29 |
The arch teams are OK with this now? If so I can go close some STABLEREQs... |
Archives