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