1 |
All, |
2 |
|
3 |
It is becoming more and more obvious that we do not have enough manpower |
4 |
on the arch teams, even some of the ones we consider major arch's, to |
5 |
keep up with stabilization requests. For example, there is this bug [1], |
6 |
which is blocking the stabilization of several important packages. |
7 |
|
8 |
I spoke to one of the team members on one of the affected arch teams on |
9 |
this bug a couple of weeks ago, and was told just that stabilization |
10 |
takes time. I pointed out that this was affecting important packages and |
11 |
I felt that the arch teams should step up their efforts when it comes to |
12 |
important packages. The arch team member disagreed unless the issue is a |
13 |
security bug. |
14 |
|
15 |
The council decision below [2] has made it possible to move on for some |
16 |
arch's by removing old stable versions of packages 90 days after the |
17 |
stable request is filed and the arch teams are added if there has been |
18 |
no action by the specific arch teams listed in the decision, and those |
19 |
arch teams are the only ones on the bug. |
20 |
|
21 |
I think we need a global policy that either helps keep the stable tree |
22 |
up to date or reverts an architecture to ~ over time if the arch team |
23 |
can't keep up. |
24 |
|
25 |
Keeping old software in the stable tree, I think we can agree, isn't |
26 |
good because newer software, besides having new features, will have bug |
27 |
fixes. |
28 |
|
29 |
Also, I think we can agree that allowing maintainers to stabilize new |
30 |
software on architectures they do not have access to wouldn't be good. |
31 |
|
32 |
I want comments wrt two ideas: |
33 |
|
34 |
1. I think maintainers should be able to stabilize their packages on arch's |
35 |
they have access to. I think this is allowed by some arch teams, but I |
36 |
think it would be good to formalize it. |
37 |
|
38 |
2. I would like to see the policy below applied to all arch's [2]. |
39 |
|
40 |
Thoughts? |
41 |
|
42 |
William |
43 |
|
44 |
[1] http://bugs.gentoo.org/487332 |
45 |
[2] http://www.gentoo.org/proj/en/council/meeting-logs/20130917-summary.txt |