On Thu, 2019-10-03 at 09:37 -0500, Chris Adams wrote:
Once upon a time, Daniel P. Berrangé <berrange(a)redhat.com>
said:
> Or just add some RPM metadata tags to record the upstream SCM type + URL +
> branch / release tag, etc. The user can thus easily find the upstream
> full commit logs corresponding to the pacakge.
IMHO that is only good when the Fedora package is nothing but the
upstream code, built with defaults. As soon as Fedora needs to add a
patch and/or systemd unit(s), change options, etc., there should be a
Fedora changelog.
Also, the current changelogs are self contained & do not
require internet access.
Remote changelog URLs might become inaccessible over time, making tracking down
behavior changes & tricky bugs problematic.
And even when it's a straight build of upstream, some maintainers
include RH Bugzilla numbers in their changelog entries, which is useful
too.
--
Chris Adams <linux(a)cmadams.net>
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org