1 |
Hello |
2 |
|
3 |
Every day I am hitting tons of blockers stabilizations and keywording |
4 |
requests for alpha, sparc, ia64, ppc and ppc64. |
5 |
|
6 |
Again, I would suggest to either decrease radically the amount of stable |
7 |
packages of some of that arches or even make them testing only. |
8 |
|
9 |
For reducing their stable tree, my suggestion would be to either keep |
10 |
their current stage3 packages stable or stage3+some concrete (and |
11 |
public) list of packages. |
12 |
|
13 |
Currently situation is not good at all as we rely on mostly one member |
14 |
needing to handle most stable work and, if any stablereq has any issue |
15 |
leading to it not being able to be handled in an "automated" way, the |
16 |
bug gets blocked for months. Also, keywording work is mostly stalled on |
17 |
this arches as it's done by even less people. |
18 |
|
19 |
The current policy of maintainers dropping keywords after 90 days is |
20 |
simply not applied because it leads up to that maintainer needing to |
21 |
kill himself that keyword and ALL the reverse deps keywords and, then, |
22 |
all that effort should probably be replaced by making the opposite, I |
23 |
mean, reducing the stable tree of that arches to a minimum and moving |
24 |
all the other packages to testing. The main advantage of this is that it |
25 |
needs maybe more effort in one round but it solves the problem for the |
26 |
future. On the other hand trying to kill keywords of a package *and all |
27 |
its reverse deps* requires a lot of work every time the problem appears. |
28 |
|
29 |
Of course I volunteer for doing the work of reducing that stable trees |
30 |
if relevant arch teams agree. |
31 |
|
32 |
Thanks a lot for your help |