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