A synthetic Release Note to identify the changes between 2 LTS versions

Hi,

Here is a suggestion from my recent experience of upgrading to an LTS version (6.7 LTS → 7.9 LTS).
Would it be possible to have a Release Note specific to the new LTS version which synthesizes all the changes since the previous LTS version?
Such a Release Note would simplify the preparation of this kind of updates by allowing faster identification of breaking changes while avoiding the tedious unstacking of all changlogs of non-LTS versions.

It was, for example, in the release note for version 7.7 that I discovered that the sonar.language key had been abandoned. It is typically this kind of information that you need to know to anticipate an LTS version upgrade.

Hi,

I’m curious whether you find the LTS-to-LTS Upgrade Notes sufficient for this or whether you’re expecting more? (Note that I’m not necessarily trying to close this out since that collection was a manual process & humans are fallible.)

 
Ann

Hi,
This is exactly what I was hoping for. Thank you for the synthesis effort.

Kenny.

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.