1 |
Problem: |
2 |
|
3 |
New stages have numerous news items listed that are likely not relevant, |
4 |
but are shown due to limitations in the filtering in NEWS items. E.g. on a |
5 |
recent stage3: |
6 |
|
7 |
nspawntest / # eselect news list |
8 |
News items: |
9 |
[1] N 2013-09-27 Separate /usr on Linux requires initramfs |
10 |
[2] N 2014-06-15 GCC 4.8.3 defaults to -fstack-protector |
11 |
[3] N 2014-10-26 GCC 4.7 Introduced the New C++11 ABI |
12 |
[4] N 2015-02-02 New portage plug-in sync system |
13 |
[5] N 2015-07-25 Python 3.4 enabled by default |
14 |
[6] N 2015-08-13 OpenSSH 7.0 disables ssh-dss keys by default |
15 |
[7] N 2015-10-22 GCC 5 Defaults to the New C++11 ABI |
16 |
[8] N 2016-06-19 L10N USE_EXPAND variable replacing LINGUAS |
17 |
[9] N 2017-11-30 New 17.0 profiles in the Gentoo repository |
18 |
|
19 |
Many of these are always displayed. For example: |
20 |
|
21 |
https://gitweb.gentoo.org/data/gentoo-news.git/tree/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt |
22 |
|
23 |
has "Display-If-Installed: sys-apps/portage" and will be displayed on |
24 |
nearly every Gentoo machine. While relevant in 2015; I'm skeptical that its |
25 |
relevant today. I am also considering explicit changes in the filtering |
26 |
directives to resolve this in the future. |
27 |
|
28 |
Glep42 states: |
29 |
|
30 |
--- |
31 |
News Item Removal |
32 |
|
33 |
News items can be removed (by removing the news file from the main tree) |
34 |
when they are no longer relevant, if they are made obsolete by a future |
35 |
news item or after a long period of time. This is the same as the method |
36 |
used for updates entries. |
37 |
--- |
38 |
|
39 |
I suggest we delete all entries prior to 2016. Git keeps history forever, |
40 |
so folks can gander at the old entries on gitweb.gentoo.org: |
41 |
|
42 |
https://gitweb.gentoo.org/data/gentoo-news.git/tree/ |
43 |
|
44 |
-A |