It is a bit tedious to publish an edition of Git Rev news and some parts of the process could easily be automated as @dscho and perhaps others already suggested. Parts that are not automated could be documented.