On 27/09/2019 00:04, Miro Hrončok wrote:
On 26. 09. 19 22:06, Jason L Tibbitts III wrote:
"C" == Christopher <ctubbsii@xxxxxxxxxxxxxxxxx> writes:
C> With version-controlled package sources, changelogs in SPEC seem so
C> obsolete to me. They are already problematic today when they conflict
C> due to changes in multiple branches.
It's important to note that the RPM changelog is rather a different
thing from a list of commits made to the specfile. If I went and
re-indented the spec, that would of course get a commit message but has
no relevance to the end user and should not result in a changelog
entry. Often I make several commits to the spec, and then update the
%changelog section with a summary of user-relevant changes only when I'm
ready to bump the release.
It seems that generating %changelog from git commits would require
something like magic tags in the commit messages, which seems like
something of a pain.
Or, as said elsewhere in this thread, we could use annotated tags.
The other possibility would be to squash commits into a single one.
Especially doing PR style makes me see commit messages like "another
fix" or "fix typo" a lot more often compared to squashed commits, where
one is working on a feature to be submitted as one commit (unlike 50
commits).
Matthias
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
