| 1 |
On Sun, 28 Jan 2007 19:17:35 +0100 (MET) Christian Faulhammer |
| 2 |
<opfer@g.o> wrote: |
| 3 |
| As we all notice from time to time, amd64 team is lacking behind a |
| 4 |
| bit, due to various reasons. a) manpower, b) a lot of keywording. |
| 5 |
| Java team asked arch teams if they object when Java team marks stable |
| 6 |
| generation-2 ebuilds on their own, due to the long time it takes and |
| 7 |
| to the amount of ebuilds to be stabilised. |
| 8 |
| So, maybe we can discuss here another helping hand for amd64. Devs |
| 9 |
| that work with a given software (not necessarily the maintainer) on |
| 10 |
| amd64 architecture and when there is a keywording bug open, then said |
| 11 |
| devs can keyword the ebuild. For a short period of time this could be |
| 12 |
| allowed to all devs. |
| 13 |
| Any objections? |
| 14 |
|
| 15 |
Why not just extend the amd64 team to include people who will only work |
| 16 |
on Java stuff? Other arch teams have no problems with developers being |
| 17 |
onboard only for a few particular packages. |
| 18 |
|
| 19 |
-- |
| 20 |
Ciaran McCreesh |
| 21 |
Mail : ciaranm at ciaranm.org |
| 22 |
Web : http://ciaranm.org/ |
| 23 |
Paludis, the secure package manager : http://paludis.pioto.org/ |
Archives