1 |
Allen Brooker wrote: |
2 |
> Donnie Berkholz wrote: |
3 |
>> Allen Brooker wrote: |
4 |
>>> Could we create a very-low-traffic, developer-posts-only list that is |
5 |
>>> used for announcing important package changes? The list could also be |
6 |
>>> used for other announcements (not sure exactly what - events where |
7 |
>>> Gentoo devs will be, regional meets, other things). If people feel that |
8 |
>>> using the same list for other announcements too would create too much |
9 |
>>> traffic, consider creating multiple lists, which would allow people to |
10 |
>>> subscribe to only the types of messages that they want to see. |
11 |
>> Just made it at the same time as this one: gentoo-dev-announce. We're |
12 |
>> still working out the policy. |
13 |
>> |
14 |
>> Thanks, |
15 |
>> Donnie |
16 |
>> |
17 |
> According to http://www.gentoo.org/main/en/lists.xml (and my impression |
18 |
> from the name) that list appears to be for developer-targeted announcements. |
19 |
> |
20 |
> What I was thinking was something along the lines of some of the |
21 |
> post-install messages (not all of them, just the important ones that |
22 |
> might actually (appear to) break things - eg. glibc upgrade - "you can't |
23 |
> downgrade"; gcc upgrade - "follow the guide here; coreutils upgrade - |
24 |
> "some locations have changed - run 'hash -r' to clear the cache"; etc.) |
25 |
> and other user-targeted messages to be sent to a list. |
26 |
> |
27 |
> Allen |
28 |
> |
29 |
On a side note, I do know there's ELOG for some of what I'm talking |
30 |
about, but as I see it the two problems with it are that: |
31 |
1) Not everyone knows about it |
32 |
2) You don't get the messages until after you've installed something. I |
33 |
believe users should have warning of "major" upgrades before they |
34 |
perform them. |
35 |
|
36 |
Allen |
37 |
|
38 |
-- |
39 |
gentoo-project@g.o mailing list |