Hi,
in June we started to be more systematic about our commit messages to
make it easier for a release manager to provide useful release notes -
by being able to point to the issues the were addressed in a specific
release [1].
However, now many of the commit messages start with "[NO ISSUE]" and
then provide a longer (but usually still very limited) description in
the commit message. This makes the creation/curation of commit messages
as cumbersome as it was before as the release manager now has to again
dig through the commit messages to be able to provide release notes.
I understand that it there’s little value in creating an issue in
order
to be able to list the issue for a small refactoring or a tiny cleanup.
But if a bug is fixed or a feature is implemented I think that it makes
a lot of sense to put the description into JIRA for easy reference by
both the commit message and the release notes.
Thoughts/concerns?
Cheers,
Till
[1]
https://lists.apache.org/thread.html/73eea2ae3cef37007d8d5fd667b16d49b7d6f131102afe6899e2dc41@%3Cdev.asterixdb.apache.org%3E
