Closed johnsimons closed 2 years ago
@slewis74 before we were merging both the "Build Information" + custom release notes as a single "release notes". This change will prevent users from doing this, do you see this as a problem?
Yeah, in the older code in the plugin it was doing some merging and plugging the result into the ReleaseNotes field for the release. The Release templates in Octopus (which can use Build Information) are separate and kick in if the ReleaseNotes on the release are left blank. So I think just leaving the release notes text field in the step here is fine.
This issue was actioned as part of https://github.com/OctopusDeploy/OctoTFS/pull/223
In V3 we used to support adding "custom release notes"
Then in V4 we decided to deprecate that feature in favour of the "Build Information" task
However Build Information is not for everyone, and some customers want to just add "Release Notes" to a release in textual format.
So in V5 we are removing the "ChangeSets and Workitems" but leaving the text field to add Release notes.
This means users can just type their release notes in the field to be included in the release.
This means users need to make a choice about release notes, they can include them manually, or use the "Build Information" task.