| 1 |
On Saturday 05 May 2007 5:34:29 pm Ciaran McCreesh wrote: |
| 2 |
> On Sat, 05 May 2007 14:26:48 -0700 |
| 3 |
> |
| 4 |
> Mike Doty <kingtaco@g.o> wrote: |
| 5 |
> > After some discussion on #-dev there are some improvements that we can |
| 6 |
> > make on glep 42. |
| 7 |
> |
| 8 |
> Well, if you're going about improving it, start by adding in the |
| 9 |
> Display-If-Upgrading-From-To: header. It'll be a nuisance to implement, |
| 10 |
> but it'll be far more useful than any of the rest of this. |
| 11 |
> |
| 12 |
> > 1. Priority levels for news items: If we did this users could decide |
| 13 |
> > what levels of importance to filter out. |
| 14 |
> |
| 15 |
> That'll just increase the amount of disagreement about news items |
| 16 |
> because it'll give people more pointless wording to argue over. |
| 17 |
> |
| 18 |
> > 2. Standards for news items: Based on the paludis news item thread, |
| 19 |
> > it's clear we need some standards for what we release as news. If |
| 20 |
> > combined with #1 we can set different standards and give the users |
| 21 |
> > some more choice on what they accept and what we publish. |
| 22 |
> |
| 23 |
> It's quite simple. If releasing a news item improves the user |
| 24 |
> experience of affected users more than not releasing it, the news item |
| 25 |
> should be released. |
| 26 |
|
| 27 |
mmm, by this arguement news should be written for every version bump, |
| 28 |
explaining what has changed in the package that is user visible. It would |
| 29 |
definatly improve the users experience if they knew what they were upgrading |
| 30 |
to, not just that they were upgrading. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
gentoo-dev@g.o mailing list |
Archives