1 |
On Tue, 20 Aug 2013 14:29:09 -0400 |
2 |
Wyatt Epp <wyatt.epp@×××××.com> wrote: |
3 |
|
4 |
> On Tue, Aug 20, 2013 at 2:19 PM, William Hubbs <williamh@g.o> |
5 |
> wrote: |
6 |
> What things in stable are undergoing bitrot? |
7 |
|
8 |
Things that are too old; see 'imlate' from app-portage/gentoolkit-dev, |
9 |
this can be handy to indicate stabilization candidates. You can try to |
10 |
filter it for things that haven't been stabilized for more than a |
11 |
month; alternatively, it's a fun data manipulation task to try to stat |
12 |
and/or grep it from the Portage tree in one or another way... |
13 |
|
14 |
> What manner of bitrot? |
15 |
|
16 |
They might ... |
17 |
|
18 |
1. ... contain stability bugs which may need fixing. |
19 |
2. ... contain security bugs that later versions have fixed. |
20 |
3. ... make it unable to file a bug upstream because it is old. |
21 |
4. ... block libraries that should otherwise be punted. |
22 |
5. ... no longer work nowadays; because some internet API changed, |
23 |
because people run a new kernel version and because ... |
24 |
6. ... and so on... |
25 |
|
26 |
In other words, it's bad QA if you keep them around for way too long. |
27 |
|
28 |
> On what architectures? |
29 |
|
30 |
There is the impression that happens on all architectures; while |
31 |
indeed, there are some minor architectures where this is a bigger |
32 |
problem, some might just benefit having no stabilization. |
33 |
|
34 |
Statistics would be nice here, because an indication is missing... |
35 |
|
36 |
> Specifics or examples seem like they'll be important here because I |
37 |
> think this is largely a matter of perception. |
38 |
|
39 |
+1 |
40 |
|
41 |
-- |
42 |
With kind regards, |
43 |
|
44 |
Tom Wijsman (TomWij) |
45 |
Gentoo Developer |
46 |
|
47 |
E-mail address : TomWij@g.o |
48 |
GPG Public Key : 6D34E57D |
49 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |