From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: modifications to GLEP42
Date: Sat, 5 May 2007 22:55:14 +0100 [thread overview]
Message-ID: <20070505225514.3ca5b131@snowflake> (raw)
In-Reply-To: <463CFAD1.70503@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
On Sat, 05 May 2007 14:44:49 -0700
Mike Doty <kingtaco@gentoo.org> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-05 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 21:26 [gentoo-dev] RFC: modifications to GLEP42 Mike Doty
2007-05-05 21:34 ` Ciaran McCreesh
2007-05-05 21:44 ` Mike Doty
2007-05-05 21:55 ` Ciaran McCreesh [this message]
2007-05-05 22:00 ` expose
2007-05-05 22:08 ` Ciaran McCreesh
2007-05-05 22:25 ` expose
2007-05-05 22:33 ` expose
2007-05-05 22:39 ` Ciaran McCreesh
2007-05-06 1:18 ` Richard Freeman
2007-05-06 2:04 ` Dan Meltzer
2007-05-06 8:54 ` Petteri Räty
2007-05-06 9:02 ` Jakub Moc
2007-05-06 9:18 ` Petteri Räty
2007-05-06 9:08 ` Marius Mauch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070505225514.3ca5b131@snowflake \
--to=ciaranm@ciaranm.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox