Change release process to accumulate releases?

[justinharringa]

Currently, we leverage the multi-module-maven-release-plugin which is great and helps us avoid manual release processes that the standard Maven release plugin requires. The only main downside that I see is that we're releasing quite a few minor changes and it seems difficult for users to get a reasonable grasp on what our releases contain due to the noise generated by tags. Release Drafter was added some time ago to help out with this when we've merged features / bug fixes that should be visible (it accumulates all of the other minor dependency bumps and other things). However, I've been toying with the idea of only publishing a new version on release.

Pros:

• Easier to grok Releases page in GitHub
• Less tags

Cons:

• All modules would revert to one release cadence so if a change were made in the primary code module, the parent pom artifact and itest artifact would also get a release version in Maven Central.
• Extra manual triage that could be forgotten

Thoughts @afalko, @npwolf, and others?

[justinharringa]

Note: This relates to #201