just mention upstream release and packaging changes
xor
add the complete changelog.
In both cases there are complaints.
And no, I won't provide an extract because I'm convinced that no packager is capable of extracting a meaningful essence from an upstream changelog.
(I further assume that upstream developers are also lazy writing docs and the changelog would have been already shorter if still meaningful.)
there is probably gonna be some bitching if we don't include a proper changelog for a version update. could you dig something up?
My way is to either
xor
In both cases there are complaints.
And no, I won't provide an extract because I'm convinced that no packager is capable of extracting a meaningful essence from an upstream changelog. (I further assume that upstream developers are also lazy writing docs and the changelog would have been already shorter if still meaningful.)
I agree with all you said, don't shoot the messenger. I particularly dislike that policy as well.. especially for semvered packages.
@matejcik: review reminder