1 |
Here's a proposal that may address concerns from the long "rfc: |
2 |
revisiting our stabilization policy" thread. |
3 |
|
4 |
It seems at least one of the problems is that with old ebuilds being |
5 |
stable on slow arches but not the more recent ebuilds, it is a |
6 |
maintenance burden to keep supporting the old ebuilds even on fast |
7 |
arches where it's still stable. |
8 |
|
9 |
Why not allow maintainers to drop redundant stable and even ~arch |
10 |
keywords from their packages? |
11 |
|
12 |
Then these old ebuilds will stay with _only_ slow arch keywords. If they |
13 |
were working back then, they will continue to work now, since there are |
14 |
not that many changes to break things as opposed to faster-moving arches. |
15 |
|
16 |
What do you think? Please let me know if I should clarify this. |
17 |
|
18 |
Paweł |