Indicate the number of major, minor and patch commits between two versions while planning

[ScopeyNZ]

Currently when releasing CWP we have to run through the entire list of modules and double check if it's worth tagging a new release. Given the large coverage of our support it's very likely that modules have had no changes since the last release. Currently this involves comparing the most recent tag with the relevant development branch and looking over the commits.

Cow could assist with this process by listing the commit messages for us and possibly providing a summary by inspecting the commit prefixes.

Example line from the plan:

[cwp/cwp-core                              ]        └ cwp/cwp-core (2.2.1) new tag, prior version 2.2.0

Idea for indicating changes

[cwp/cwp-core                              ]        └ cwp/cwp-core (2.2.1) new tag, prior version 2.2.0 (2M, 3m, 4p, 1?)
[cwp/cwp-core                              ]        └ cwp/cwp-core (2.2.1) new tag, prior version 2.2.0 (No changes)
[cwp/cwp-core                              ]        └ cwp/cwp-core (2.2.1) new tag, prior version 2.2.0 (3?)

This lists the major (M), minor (m), patch (p) and unspecified (?) commits. Example output for updating the tag on a module in the plan:

Please enter a new version to release for cwp/cwp-core:

We could simply just list a limited set of commits above this:

* FIX Something was fixed
* NEW I added something
* API I broke something
* Travis updates
Summary: 1M, 1m, 1p, 1? - Compare at https://github.com/silverstripe/cwp/compare/2.2.2...2.2
---
Please enter a new version to release for cwp/cwp-core:

[robbieaverill]

I kind of feel like it would be better to provide a GitHub compare link to check these things manually. Not sure I like this idea TBH

[ScopeyNZ]

provide a GitHub compare link

I put that in my example 😅

[brynwhyman]

Is this the parent issue for #144?

[ScopeyNZ]

Yes might as well be.