dashorst opened a new issue, #1875:
URL: https://github.com/apache/wicket/issues/1875
The release notes that `build-changelog.sh` builds list issues by type, key
and title, but not who did the work. A contributor is credited only as the
author of a commit. Release notes should thank the people who contributed to
the release, and welcome the ones who contributed for the first time.
## Proposal
Add a contributors section at the end of each release's notes:
```
** Contributors
Thanks to the 9 people who contributed to this release, and a
welcome to those who did so for the first time: Swarneil1905, …
```
- **Contributors** are the commit authors in the release range, the same
range the script already reads the GitHub issue references from, plus anyone
named in a `Co-authored-by:` trailer.
- **First-time contributors** are those without a commit in any earlier
release tag, on any branch. Cherry-picks keep the original author, so a fix
that lands on several lines welcomes its author in whichever release ships
first. Releases cut on the same day each welcome them, which is fine.
## Prerequisite: `.mailmap`
People who committed under several names or addresses (an employer's
address, a personal one, apache.org) would be counted more than once, or
welcomed as new by mistake. A `.mailmap` in the repository root maps them to
one identity. `git log` applies it through `%aN`/`%aE`, so the script needs no
lookup of its own.
## Open points
- Plain names are enough for the plain-text changelog. The announcement
email or a GitHub post could use `@login`, looked up per commit through `gh
api`, which also resolves commits made under GitHub's noreply address.
- Should committers be listed among the contributors, or only people without
commit access?
Follows #1699.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
