Re: Bug#190302: Misusage of changelog!
Luca - De Whiskey's - De Vitis <email@example.com> a tapoté :
> > You said you have "to list each change in the upstream changelog" to
> > know which bug can be declared as closed. And that's, as maintainer,
> > your job, isn't it? But is it users job to do it too?
> I do not understand that: could you rephrase?
You wrote that you have "to list each change in the upstream
changelog" to know which bug can be declared as closed. Right?
You need to do that as the maintainer. Right?
Do you think that users should list "each change in the upstream
changelog" to know how the bug they submitted as been closed?
> > You still did not answer to the question: is it too much extra work
> > you can afford to add in the changelog what permits you to declare a
> > bug closed?
> Speaking about entry like "New upstream closes #...", my position is:
> This kind of request is futile, redundant and of no real need in _any_ case.
> Hunting maintainers down for a log entry of that kind is a waste of time
> either for the maintainer and for the hunters. All the arguments brought to
> this discussion to confute my observation are so childish and contraddictory,
> that the only way i have to demonstrate it is to act as previously stated.
So the only way you have to demonstrate it is to act as a child?
You do not think that providing these info in the changelog is
useful. That your choice. But apparently many people disagree with
You have an easy solution: follow the 4. of the Debian social
contract ( http://www.debian.org/social_contract ).
Not a native english speaker: