|
Lines 222-235
This also applies to revision bumps, not just to upstream version changes.
Link Here
|
| 222 |
<body> |
222 |
<body> |
| 223 |
|
223 |
|
| 224 |
<p> |
224 |
<p> |
| 225 |
Moving a package from <c>~arch</c> to <c>arch</c> is done only by the relevant arch teams. |
225 |
Only the relevant arch teams may move a package from <c>~arch</c> to |
| 226 |
If you have access to non-x86 hardware but are not on the arch teams, you may wish |
226 |
<c>arch</c>. We make an exception to this rule for <c>x86</c> and |
| 227 |
to make individual arrangements <d /> the arch teams are happy for help, so long as |
227 |
<c>amd64</c>: these arches may be stabilized by a maintainer who |
| 228 |
they know what is going on. Please note that <c>x86</c> is now no longer an exception |
228 |
has the hardware and a stable system to use for testing. |
| 229 |
and stabilisation must be done through the <c>x86</c> arch team unless you have |
229 |
</p> |
| 230 |
individual arrangements <d /> see |
230 |
<p> |
| 231 |
<uri link="https://wiki.gentoo.org/wiki/GLEP:40">GLEP 40</uri> |
231 |
If you have access to non-<c>x86</c>/<c>amd64</c> hardware but are |
| 232 |
for further details. |
232 |
not on the associated arch team, you may wish to make individual |
|
|
233 |
arrangements<d />the arch teams are happy for help, so long as they |
| 234 |
know what is going on. |
| 233 |
</p> |
235 |
</p> |
| 234 |
|
236 |
|
| 235 |
<p> |
237 |
<p> |
| 236 |
- |
|
|
