| 1 |
On Sat, 05 May 2007 15:15:55 +0200 |
| 2 |
Jakub Moc <jakub@g.o> wrote: |
| 3 |
> > Only Paludis users will use the news item. To Paludis users, the |
| 4 |
> > news item is not a triviality or noise. To everyone else it's |
| 5 |
> > irrelevant. |
| 6 |
> |
| 7 |
> How does it matter exactly whether it's paludis users, gcc users, php |
| 8 |
> users, apache users or whoever else who will use the news item? Let's |
| 9 |
> not misuse news framework for stuff that |
| 10 |
|
| 11 |
Er, that's one of the main points of GLEP 42's design: it allows |
| 12 |
delivery of news items that are important to a subset of users only to |
| 13 |
that subset. The size of the subset is entirely irrelevant. |
| 14 |
|
| 15 |
> For this particular case, you can (and do even) advise specifically |
| 16 |
> the affected users only on runtime that the config files syntax has |
| 17 |
> been changed. (Frankly, you don't even need elog stuff for similar |
| 18 |
> things; everyone concerned will get the message paludis spits on the |
| 19 |
> screen when they try to use it). |
| 20 |
|
| 21 |
Experience and user feedback has shown that in situations like this |
| 22 |
users want an accompanying news item even if the application does output |
| 23 |
deprecation warnings. |
| 24 |
|
| 25 |
-- |
| 26 |
Ciaran McCreesh |
Archives