We don't want to include the header in the GitHub releases, as we will
end up with two headers with the same value. Considering that we are
thinking of fully automating patch releases, this change helps with that
too. Small steps.
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Mentioning the release-notes change is important, as we want to change
the way contributors (including us) make changes. Release notes should
be part of the change, and the reasoning behind it is in the 3.9.2
release notes.
Removing any mention of the Grafana dashboard as it is not something
that end-users will see. We didn't mention it in the 3.9.1 release
notes, and we are even thinking of removing all Grafana dashboards from
rabbitmq_prometheus. This explains why:
https://github.com/rabbitmq/release-engineering/issues/11#issuecomment-887627938
cc @michaelklishin
Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk>
Keeping them in this repo might encourage more people to update
them as changes are merged, and simplify release automation a bit.
So let's try it. Per suggestion from @gerhard.
Michael Klishin
Gerhard Lazu
Michael Klishin