On Sat, 05 May 2007 14:44:49 -0700 Mike Doty <[EMAIL PROTECTED]> wrote: > > Well, if you're going about improving it, start by adding in the > > Display-If-Upgrading-From-To: header. It'll be a nuisance to > > implement, but it'll be far more useful than any of the rest of > > this. > > Your word doesn't inspire most of us. If you think this is a good > idea, you need to explain why.
There's no way to mark a news item as "to be read" when a user upgrades from, say, <foo/bar-1.2 to >=foo/bar-1.2 . Ideally there would be. It wasn't in the first GLEP because it's trickier from a package manager implementation perspective. > >> 2. Standards for news items: Based on the paludis news item > >> thread, it's clear we need some standards for what we release as > >> news. If combined with #1 we can set different standards and give > >> the users some more choice on what they accept and what we publish. > > > > It's quite simple. If releasing a news item improves the user > > experience of affected users more than not releasing it, the news > > item should be released. > > It clearly isn't that simple. Well, it is in theory. In practice determining into which category a particular news item falls isn't so easy. Perhaps this should be left alone until after we have experience delivering, say, a few dozen news items to a wider audience. Currently the only evidence we have as to the level of news items expected by users is fairly limited. -- Ciaran McCreesh
signature.asc
Description: PGP signature
