I don't think this works well:
On 14.03.17 14:04, Julian Reschke wrote:
Let me suggest something else: a) follow commit emails,
As outlined in my previous mail this distributes the effort of figuring out the particulars of a backport to every committer where it would be less effort to just write a single short message to @oak-dev. Also due to the large volume of traffic on @commits it is too easy to miss something.
b) when we do a release from a stable branch, actually review what changed, instead of just ~3 people only running the release checker script.
The release process is mostly about compliance with ASF licence requirements [1]. Apart from that when releasing it is not the appropriate time to discuss individual issues, their potential impact and risks. This is too late in the game. Such issues should be discussed close to the time when they are being worked on.
Michael [1] http://www.apache.org/dev/release-publishing.html
