1 |
Pawel, |
2 |
|
3 |
while I appreciate very much what you are doing, there is one obvious problem: usually, as a maintainer, one does not file a stablereq for a single arch, but for all stable arches of a package. |
4 |
|
5 |
Are the cited advances relevant for all stable arches, for the "major ones", or only for one of them? |
6 |
|
7 |
I would like to avoid the situation that we all file stable requests like mad and end up with all-but-one swamped arch teams and a neverending list of open stabilization bugs waiting for the last arch. |
8 |
|
9 |
Cheers, |
10 |
Andreas |
11 |
|
12 |
|
13 |
Am Montag 21 November 2011, 09:41:07 schrieb Paweł Hajdan, Jr.: |
14 |
> I think that with recent advancements in batch-stabilization we're able |
15 |
> to process a much higher amount of stabilization bugs, and keep the bug |
16 |
> queue low. It used to be longer than 100 bugs, but now it's closer to |
17 |
> 20-30 bugs for which regressions or other problems have been detected. |
18 |
> |
19 |
> This allows us to do better testing of the stabilization candidates, but |
20 |
> also I think we should start bringing even more updates to the stable tree. |
21 |
> |
22 |
> When doing stable testing I frequently notice bugs fixed in ~arch but |
23 |
> not stabilized, so stable is frequently affected by problems that could |
24 |
> be easily fixed by stabilizing a more recent version. |
25 |
> |
26 |
> I wrote a script, |
27 |
> <http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=blob;f=stabilization-candidates.py;hb=HEAD>, |
28 |
> that scans the tree for packages that could be easily stabilized (all |
29 |
> deps stable, no bugs). |
30 |
> |
31 |
> I'm attaching a list of packages that are sitting in the tree for at |
32 |
> least 6 months (180 days, way more than 30 days required for |
33 |
> stabilization) and should be ready for stabilization. |
34 |
> |
35 |
> Please review the list, it's 800+ packages so I thought about asking for |
36 |
> feedback before filing stabilization bugs (I plan to do that in stages |
37 |
> of course). |
38 |
> |
39 |
> Paweł |
40 |
> |
41 |
|
42 |
|
43 |
-- |
44 |
Andreas K. Huettel |
45 |
Gentoo Linux developer - kde, sci, arm, tex |
46 |
dilfridge@g.o |
47 |
http://www.akhuettel.de/ |