URL:
https://github.com/SSSD/sssd/pull/5257
Title: #5257: git-template: add tags to help with release notes automation
elkoniu commented:
"""
I like the idea. So it works like some journal file where each commit adds
record about changes and then this file is consumed by release and cleaned?
pt., 14 sie 2020, 13:57 użytkownik Pavel Březina <notifications(a)github.com>
napisał:
When I submitted a contribution to Ansible, they wanted me to provide
a release
notes fragment <
https://github.com/ansible/ansible/tree/devel/changelogs>.
Little digging revealed that they are using a tool reno
<
https://docs.openstack.org/reno/latest/user/usage.html> developed by
Openstack. The idea is similar to what I suggested but instead of
describing the changes in a commit message you describe it in a file. The
files are deleted with new release. One of the advantages in this approach
is that it can actually detect that a patch was reverted (the file is not
present anymore) and you can fix typos any time which would be hard if it
is in commit message.
I believe this is worth trying out. We wouldn't have to implement the
parser ourselves, it seems to be flexible and it can be directly integrated
with sphinx. It would also make it easier to provide more granularity as
Pawel suggested. And of course we will not be hitting this silly conflict
with emojis :-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/SSSD/sssd/pull/5257#issuecomment-674039408>, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AARUPLG5OB4FG6F3WYSM64T...
.
"""
See the full comment at
https://github.com/SSSD/sssd/pull/5257#issuecomment-674358906