+2017 (given that we may miss the year :) ) I think I've raised same discussion (exactly same approach: Spark solution) for several times. I'd like to automate as many as possible, instead of requiring us to be more diligent*.*
- Jungtaek Lim (HeartSaVioR) 2017년 12월 23일 (토) 오전 3:20, Stig Rohde Døssing <[email protected]>님이 작성: > Hi everyone. > > The contributors list in the README seems fairly out of date. Updating it > manually when a new contributor gets their PR merged is pretty easy to > forget, it's basically the same issue we had with CHANGELOG.md. How would > people feel about adding a script to generate the contributor list for each > release? We could look at JIRA assignees, or commit authors or some other > option? > > Took a quick look at a couple of other Apache projects. > > Zookeeper links to their JIRA on their credits page instead of providing a > separate list of contributors > https://zookeeper.apache.org/credits.html#contributors. > > Spark generates a list of contributors as part of their release notes > https://spark.apache.org/releases/spark-release-2-0-0.html#credits from > commit authors since last release > > https://github.com/apache/spark/blob/master/dev/create-release/generate-contributors.py > . > > I'd be for the Spark solution if it doesn't introduce too much hassle in > the release process. Does anyone have an opinion on this? >
