1 |
On 12/11/05, Wernfried Haas <amne@g.o> wrote: |
2 |
> On Sun, Dec 11, 2005 at 01:35:50AM +0000, Ciaran McCreesh wrote: |
3 |
> > Although most package updates are clean and require little user action, |
4 |
> > occasionally an upgrade requires user intervention during the upgrade process. |
5 |
> > Recent examples of the latter include the ``gcc-3.4`` stabilisation on ``x86`` |
6 |
> > and the ``mysql-5`` database format changes. |
7 |
> > |
8 |
> > There are currently several ways of delivering important news items to our |
9 |
> > users, none of them particularly effective: |
10 |
> |
11 |
> I'd suggest changing this to something more constructive - calling our |
12 |
> current efforts "none of them particularly effective" isn't exactly |
13 |
> a constructive way of critizing things. |
14 |
> |
15 |
> > * Gentoo Weekly News |
16 |
> > * The ``gentoo-announce``, ``gentoo-user`` and ``gentoo-dev`` mailing lists |
17 |
> > * The Gentoo Forums |
18 |
> > * The main Gentoo website |
19 |
> > * RSS feeds of Gentoo news |
20 |
> |
21 |
> Einfo is currently being used for that purpose as well - even if the |
22 |
> GLEP will leave it for less important news in the future. So i guess |
23 |
> it should be listed here. |
24 |
> |
25 |
> > A more reliable way of getting news of critical updates out to users is required |
26 |
> > to avoid repeats of the various recent upgrade debacles. |
27 |
> |
28 |
> As it was mentioned above, gcc 3.4 went pretty well on x86, can't |
29 |
> comment on mysql as i don't use it myself. I'd suggest changing this |
30 |
> text for something more diplomatic as i don't see much sense in having |
31 |
> council approved GLEPs talking about council approved upgrade debacles. |
32 |
> I'd suggest: |
33 |
> "A more reliable way of getting news of critical updates out to users is required |
34 |
> to prevent problems during upgrades." |
35 |
|
36 |
My opinion? The gcc-3.4 upgrade has appeared to go fairly well because |
37 |
it doesn't automagically upgrade, it requires manual intervention |
38 |
before it is used. People see this and investigate. This is not |
39 |
something that always happens (apache anyone?, baselayout ~arch |
40 |
anyone?) And due to this, I don't believe we can judge success on the |
41 |
gcc upgrade alone. |
42 |
|
43 |
> |
44 |
> > .. Important:: This GLEP does not seek to replace or modify ``einfo`` messages |
45 |
> > which are displayed post-install. That is a separate issue which is handled |
46 |
> > by ``elog`` [#bug-11359]_. |
47 |
> |
48 |
> Thanks for clearing this quite important point up. |
49 |
> |
50 |
> > Thus, at least 72 hours before a proposed news item is committed, it must be |
51 |
> > posted to the ``gentoo-dev`` mailing list and ``Cc:``\ed to ``pr@g.o`` |
52 |
> > (exceptions may be made in exceptional circumstances). Any complaints ??? for |
53 |
> > example regarding wording, clarity or accuracy ??? **must** be addressed before |
54 |
> > the news item goes live. |
55 |
> |
56 |
> I know you think it is beyond the scope of this GLEP, but i believe |
57 |
> having a new tool with rules for publication and OTOH all the |
58 |
> old tools mentioned above without clear guidelines/hints how to use |
59 |
> them doesn't make perfect sense. The gcc upgrade on x86 has shown so |
60 |
> far that combining our efforts does work quite well. Even if not |
61 |
> within this GLEP there should be some documentation how to make use of |
62 |
> all available tools to inform users. Otherwise we just have another |
63 |
> tool that gets more or less acceptance within the community. |
64 |
> |
65 |
> I'd suggest extending the process of creating a news item to also |
66 |
> create a text to be posted to www.gentoo.org, the |
67 |
> announce-mailinglist, the forums, RSS feeds, GWN, etc. Of course |
68 |
> depending on the importance it may be decided to e.g. not post it |
69 |
> on announce but only www.gentoo.org. |
70 |
> |
71 |
> Do you think this can be done within this GLEP or rather outside? |
72 |
> |
73 |
> cheers, |
74 |
> Wernfried |
75 |
> |
76 |
> -- |
77 |
> Wernfried Haas (amne) - amne at gentoo dot org |
78 |
> Gentoo Forums: http://forums.gentoo.org |
79 |
> IRC: #gentoo-forums on freenode - email: forum-mods at gentoo dot org |
80 |
> -- |
81 |
> gentoo-dev@g.o mailing list |
82 |
> |
83 |
> |
84 |
|
85 |
-- |
86 |
gentoo-dev@g.o mailing list |