At this point we have quite lean publishing of release announcements. However (from my own experience as a maintainer of several modules) it’s sometimes not only cumbersome but challenging to write something more that what is automatically generated. There are several reasons for that, but the most important is that at the point when given component is released you don’t really remember what were the highlights and why they are worth mentioning besides automated issues list.
So I came up with the idea of making “the process” better. Here’s what I have in mind:
- Every important commit going to master is titled in a shape that it can be re-used (or slightly rephrased)
- If particular commit has a git note attached to it in the namespace of
refs/notes/blogthen it should be considered as something automatically pulled to the blog announcement
This has main benefit of announcing the release at the same time as it actually happens (hopefully after mvn central gets synced :D) with (hopefully) appealing content.
Now there is one open questions I would like to gather some feedback about (besides the one if you find this idea useful)
- What if there are no notes? Shall we just do regular automated announcement?
@aslak Can you point me to the release announcement generator code? Are we also synced with Twitter to spread the word even more?