1 |
W dniu wto, 02.01.2018 o godzinie 19∶13 -0500, użytkownik Alec Warner |
2 |
napisał: |
3 |
> Problem: |
4 |
> |
5 |
> New stages have numerous news items listed that are likely not relevant, |
6 |
> but are shown due to limitations in the filtering in NEWS items. E.g. on a |
7 |
> recent stage3: |
8 |
> |
9 |
> nspawntest / # eselect news list |
10 |
> News items: |
11 |
> [1] N 2013-09-27 Separate /usr on Linux requires initramfs |
12 |
> [2] N 2014-06-15 GCC 4.8.3 defaults to -fstack-protector |
13 |
> [3] N 2014-10-26 GCC 4.7 Introduced the New C++11 ABI |
14 |
> [4] N 2015-02-02 New portage plug-in sync system |
15 |
> [5] N 2015-07-25 Python 3.4 enabled by default |
16 |
> [6] N 2015-08-13 OpenSSH 7.0 disables ssh-dss keys by default |
17 |
> [7] N 2015-10-22 GCC 5 Defaults to the New C++11 ABI |
18 |
> [8] N 2016-06-19 L10N USE_EXPAND variable replacing LINGUAS |
19 |
> [9] N 2017-11-30 New 17.0 profiles in the Gentoo repository |
20 |
> |
21 |
> Many of these are always displayed. For example: |
22 |
> |
23 |
> https://gitweb.gentoo.org/data/gentoo-news.git/tree/2015-02-04-portage-sync-changes/2015-02-04-portage-sync-changes.en.txt |
24 |
> |
25 |
> has "Display-If-Installed: sys-apps/portage" and will be displayed on |
26 |
> nearly every Gentoo machine. While relevant in 2015; I'm skeptical that its |
27 |
> relevant today. I am also considering explicit changes in the filtering |
28 |
> directives to resolve this in the future. |
29 |
> |
30 |
> Glep42 states: |
31 |
> |
32 |
> --- |
33 |
> News Item Removal |
34 |
> |
35 |
> News items can be removed (by removing the news file from the main tree) |
36 |
> when they are no longer relevant, if they are made obsolete by a future |
37 |
> news item or after a long period of time. This is the same as the method |
38 |
> used for updates entries. |
39 |
> --- |
40 |
> |
41 |
> I suggest we delete all entries prior to 2016. Git keeps history forever, |
42 |
> so folks can gander at the old entries on gitweb.gentoo.org: |
43 |
> |
44 |
|
45 |
For completeness, I should point out that I've seen one user complaining |
46 |
about old news items disappearing. While I support the motion, I think |
47 |
we should take some care to make sure that there is some 'replacement' |
48 |
documentation for the things announced by news items. |
49 |
|
50 |
In other words, it's a bad idea to remove news items when the available |
51 |
documentation explains the 'before' state and the news item is the only |
52 |
source of information of the 'after' state. |
53 |
|
54 |
-- |
55 |
Best regards, |
56 |
Michał Górny |