1 |
The attached patch proposes a new news item format (2.1). |
2 |
|
3 |
In format 2.1, the Expires: header is mandatory. |
4 |
|
5 |
PMs can detect whether a given news item is "expired" by comparing the |
6 |
current date in UTC to the expired date. |
7 |
Expired news items should not be shown to users. |
8 |
|
9 |
Once this is accepted and implemented, we can go back and bump the existing |
10 |
news items to format 2.1 and add the new mandatory header. |
11 |
|
12 |
Old news implementations should ignore the "Expires" header (as they ignore |
13 |
any unspecified header.) |
14 |
|
15 |
|
16 |
|
17 |
On Wed, Jan 3, 2018 at 10:16 AM, Alec Warner <antarus@g.o> wrote: |
18 |
|
19 |
> |
20 |
> |
21 |
> On Wed, Jan 3, 2018 at 6:07 AM, Ulrich Mueller <ulm@g.o> wrote: |
22 |
> |
23 |
>> >>>>> On Tue, 2 Jan 2018, Alec Warner wrote: |
24 |
>> |
25 |
>> > Problem: |
26 |
>> > New stages have numerous news items listed that are likely not |
27 |
>> > relevant, but are shown due to limitations in the filtering in NEWS |
28 |
>> > items. E.g. on a recent stage3: |
29 |
>> |
30 |
>> > [...] |
31 |
>> |
32 |
>> We could add an "Expires:" header to the news item format, and the |
33 |
>> package manager (or eselect news) could mask old items based on it. |
34 |
>> |
35 |
> |
36 |
> Ok, I'll submit a patch to the GLEP for this. Stay tuned. |
37 |
> |
38 |
> -A |
39 |
> |
40 |
> |
41 |
>> |
42 |
>> Ulrich |
43 |
>> |
44 |
> |
45 |
> |