Managing the Changelog

[danehans]

The changelog was not updated as part of the RC1 release. A changelog was generated as part of the release. Should we remove the existing changelog and just use the GH release changelogs?

cc: @youngnick @LukeShu @arkodg

[arkodg]

• for now, we could leave the generated CHANGELOG as is, and maybe cleanup the older https://github.com/envoyproxy/gateway/tree/main/changelogs
• the GHA https://github.com/softprops/action-gh-release#-external-release-notes allows us to use any external Changelog generator For rc2 we should consider something more sophisticated that is based off contents/labels in the PRs

[danehans]

xref #325

[danehans]

Reopened this issue to act as a recurring reminder to create a changelog per release.

[danehans]

This issue can be reclosed after https://github.com/envoyproxy/gateway/pull/325 has been merged.

[arkodg]

I liked how https://github.com/envoyproxy/gateway/releases/tag/v0.2.0-rc1 acknowledged community contributions, we should consider something similar going forward

[danehans]

@arkodg regarding https://github.com/envoyproxy/gateway/issues/324#issuecomment-1263820704, GitHub automatically acknowledges new contributors when cutting a release. The same was done for RC1.

[arkodg]

yeah looks like we've preserved it, which is great :) , but now i'm confused as to how https://github.com/envoyproxy/gateway/blob/main/changelogs/0.2.0-rc2.yaml is being presented to the user

[danehans]

Update changelog -> release notes.

[danehans]

Closed by https://github.com/envoyproxy/gateway/pull/475