1 |
Aaron W. Swenson posted on Thu, 19 Sep 2013 20:36:50 +0000 as excerpted: |
2 |
|
3 |
> On 2013-09-19 21:29, Andreas K. Huettel wrote: |
4 |
>> |
5 |
>> For general review and improvement, to be committed 2013-09-25... [The |
6 |
>> summary link [3] will work soon... :) ] |
7 |
>> |
8 |
>> ################## |
9 |
>> |
10 |
>> Title: m68k, s390, and sh are dropping stable keywords |
11 |
> |
12 |
> To stay within 42 characters, perhaps rewrite the title as: |
13 |
> Drop Stable Keyword for m68k, s390, and sh |
14 |
> |
15 |
> Or: |
16 |
> m68k, s390, and sh Move to Unstable |
17 |
|
18 |
Or even just drop "and" and replacing "are" with a colon (assuming a |
19 |
colon is allowed): |
20 |
|
21 |
m68k, s390, sh: Dropping stable keywords |
22 |
|
23 |
>> Following discussion [1] and a vote by the Gentoo Council [2,3], m68k, |
24 |
>> s390, and sh will drop all stable keywords and become unstable/testing |
25 |
>> only arches. The main reason for this is that these arch teams visibly |
26 |
>> lack manpower, leading to overall delays. |
27 |
>> Stable may well be synonymous with outdated here. |
28 |
> |
29 |
> I would remove the last sentence. It read a bit as editorializing. |
30 |
> However, I'd change "leading to overall delays" to "which resulted in |
31 |
> undesirable delays". |
32 |
|
33 |
Or "resulting in undesirable delays." |
34 |
|
35 |
But remembering this is targeted at users, I'd keep but change the last |
36 |
sentence as well, as "outdated" or more specifically "insecure" is likely |
37 |
to be the big user-viewpoint concern that this should address. |
38 |
|
39 |
"The concern is that stable thus risked being synonymous with dated and |
40 |
possibly insecure, such that dropping it seemed the best and most |
41 |
practical way forward." |
42 |
|
43 |
But dropping the sentence entirely works too; I just think users might be |
44 |
left wondering why they can't simply keep existing stable only and not |
45 |
update, and this sentence makes explicit the ultimate risk in that. But |
46 |
perhaps that explicitness isn't necessary. |
47 |
|
48 |
>> No steps are required from users, however you should be aware of the |
49 |
>> upcoming changes. |
50 |
> |
51 |
> I'd "bottom line" this as: |
52 |
> No action is required to prepare for this change. |
53 |
> |
54 |
> Of course, just my 2¢. |
55 |
|
56 |
"This notice is for information only. No user action required." |
57 |
|
58 |
... And that could either remain at the bottom, or be moved to be the |
59 |
first paragraph. |
60 |
|
61 |
Talking about which... perhaps making it a general practice to make the |
62 |
first sentence/paragraph either "notice only", or "user action required", |
63 |
would be a good idea? Maybe even promote it to a general header |
64 |
("Action status: Notice only", "Action status: Action required" ?), so |
65 |
readers/tools that wish to can sort by it? |
66 |
|
67 |
-- |
68 |
Duncan - List replies preferred. No HTML msgs. |
69 |
"Every nonfree program has a lord, a master -- |
70 |
and if you use the program, he is your master." Richard Stallman |