Include GovCMS distribution information in release notes

[Benjen]

There seems to be inconsistency in documenting GovCMS distribution version changes in release notes. The last release to specifically mention a change to GovCMS distro version was v8.9.1. Given that v8.9.3 contains Drupal core 8.9.3 which is part of GovCMS 1.8.0, then I presume GovCMS distro 1.8.0 was included in release v8.9.3.

It would be good to be consistent in providing this information. The reason for this is that we are creating a starter kit for GovCMS8 and need to be able to keep track of distro updates so that we can make sure relevant config changes are updated and exported for our starter kit. We do this by manually updating the GovCMS image version (e.g. 8.9.3) in the starter kit config and then running and exporting any database updates.

The problem is that when GovCMS updates the distribution, they send a notification specifying the distro version (e.g. 1.8.0) rather than the image version (e.g. 8.9.3). It is then up to us to map the distro version to the corresponding image version. This would be a lot easier if the image version release notes made mention of what distro version it is using.

[fubarhouse]

@Benjen,

I'm having some difficulty understanding exactly where the issue in communications is. Are you able to provide an example of what you would expect to read ideally?

Links to releases could also help guide any changes to how releases are communicated, or references to versions which customers receive alerts via the service desk?