1 |
On Mon, Jan 12, 2009 at 3:05 AM, AllenJB <gentoo-lists@××××××××××.uk> wrote: |
2 |
> Peter Volkov wrote: |
3 |
>> |
4 |
>> В Вск, 11/01/2009 в 10:31 +0100, Benedikt Böhm пишет: |
5 |
>>> |
6 |
>>> On Sun, Jan 11, 2009 at 01:56:52AM +0100, Friedrich Oslage wrote: |
7 |
>>>> |
8 |
>>>> - - you forgot the ChangeLog entry |
9 |
>>> |
10 |
>>> `cvs log` is the changelog, i don't see why i should add a changelog |
11 |
>>> entry. |
12 |
>> |
13 |
>> There is the same reason as for ChangeLogs for ebuilds. Users (I'm user |
14 |
>> too) don't have cvs log at hand at their systems but still consider that |
15 |
>> it's important to know about changes. |
16 |
>> |
17 |
>> Is it really hard to script `echangelog "msg" && cvs commit -m "msg"`? |
18 |
>> |
19 |
> In my opinion the cvs commit log and the ChangeLog serve 2 different |
20 |
> purposes. The cvs log is for developers while the ChangeLog is for users. |
21 |
> While the cvs log will likely just want to explain what change was made, the |
22 |
> ChangeLog should explain why it was made. |
23 |
> |
24 |
> Developers need to realise that users don't know everything about the |
25 |
> software they use and don't always pin down the reasons for unexpected |
26 |
> beviour. Users also don't always read the documentation given to them. |
27 |
> |
28 |
> This has been seen recently in the change of default behavior of the world |
29 |
> set in stable portage is a good example of this. Many users didn't even know |
30 |
> about the --update option and many don't read post-commit messages (I expect |
31 |
> because they don't realise the importance of those messages or how they can |
32 |
> change the ELOG options to make the messages easier to read, for example by |
33 |
> having them emailed to them). |
34 |
> |
35 |
> There are other examples of insufficient information being given to users |
36 |
> too - the dvdnav USE flag was masked recently, but neither the ChangeLog or |
37 |
> the cvs commit message give any indication as to why this occurred. |
38 |
> |
39 |
> In my opinion Gentoo developers need to do more to communicate with their |
40 |
> users. This could be as simple as prominently posting documentation on the |
41 |
> elog system and how to tailor it. Or it might involve posting more |
42 |
> announcements to the Gentoo website (which would double up and make the |
43 |
> project look more active than it currently does from its front page). |
44 |
|
45 |
It sounds like you just volunteered to write an article on elog for |
46 |
the GMN...am I reading your post correctly? :) |
47 |
|
48 |
> |
49 |
> AllenJB |
50 |
> |
51 |
> PS. I know about index2.xml - but that doesn't look like it's going to be |
52 |
> the main front page any time soon at the moment, which is a real shame |
53 |
> because it has some awesome changes. |
54 |
> |
55 |
> |