1 |
Ciaran McCreesh <ciaranm@×××××××.org>: |
2 |
|
3 |
> On Sun, 28 Jan 2007 19:17:35 +0100 (MET) Christian Faulhammer |
4 |
> <opfer@g.o> wrote: |
5 |
> | As we all notice from time to time, amd64 team is lacking behind a |
6 |
> | bit, due to various reasons. a) manpower, b) a lot of keywording. |
7 |
> | Java team asked arch teams if they object when Java team marks |
8 |
> stable | generation-2 ebuilds on their own, due to the long time it |
9 |
> takes and | to the amount of ebuilds to be stabilised. |
10 |
> | So, maybe we can discuss here another helping hand for amd64. Devs |
11 |
> | that work with a given software (not necessarily the maintainer) on |
12 |
> | amd64 architecture and when there is a keywording bug open, then |
13 |
> said | devs can keyword the ebuild. For a short period of time this |
14 |
> could be | allowed to all devs. |
15 |
> | Any objections? |
16 |
> Why not just extend the amd64 team to include people who will only |
17 |
> work on Java stuff? Other arch teams have no problems with developers |
18 |
> being onboard only for a few particular packages. |
19 |
|
20 |
Because it was meant for every package and I only talk about |
21 |
keywording ~amd64, not stabling. The latter is handled by the team in |
22 |
a timely manner, but keywording is put aside (it leads to even more |
23 |
stabling, once it is keyworded). Java was only mentioned, as they came |
24 |
up with an idea to help amd64 in special and arch teams in general. |
25 |
|
26 |
V-Li |