[x] If any changes are made in the harvest autosupport repository, please update the harvest-metrics repository main branch with the latest asup_linux_amd64 binary. This binary can be generated using Jenkins with the following parameters:
Field
Value
VERSION
24.05.2
RELEASE
1
BRANCH
release/24.05.2
ASUP_MAKE_TARGET
production
DOCKER_PUBLISH
false
RUN_TEST
true
OVERWRITE_DOCKER_LATEST_TAG
false
[x] Create a release branch for the harvest-metrics repo like so:
[x] Ensure all issues for the release are tagged with status/testme and unassigned. Use gh or the GitHub UI to do this.
[x] Use the release issue burn down list to verify issues are fixed. Move status/testme issues to status/open or status/done
[x] Ensure that the release is validated against NABox.
[x] Ensure that the release is validated against FSX.
[x] Use Jenkins to create release artifacts for test machines
[x] Create changelog
[x] Draft a new release. Use v$RELEASE for the tag and pick the release/$RELEASE branch. Click the Generate release notes button and double check, at the bottom of the release notes, that the commits are across the correct range. For example: https://github.com/NetApp/harvest/compare/v24.05.1...v24.05.2
[x] Copy/paste the generated release notes and save them in a file pbpaste > ghrn_$RELEASE.md
[x] Generate draft release highlights by executing go run pkg/changelog/main.go new. This will create a file named releaseHighlights_$RELEASE.md. Edit that file to add content (example content)
[x] Ensure all notable features are highlighted
[x] Ensure any breaking changes are highlighted
[x] Ensure any deprecations are highlighted
[x] Generate changelog by running
go run pkg/changelog/main.go --title $RELEASE --highlights releaseHighlights_$RELEASE.md -r ghrn_$RELEASE.md | pbcopy
[x] Open a PR against the release branch with the generated release notes for review
[x] PR approval
Update Metrics Documentation
bin/harvest generate metrics --poller POLLERNAME
[x] Make sure docs look good and open a PR for review with docs/ontap-metrics.md changes
The week before the release
main
branch with the latestasup_linux_amd64
binary. This binary can be generated using Jenkins with the following parameters:status/testme
and unassigned. Usegh
or the GitHub UI to do this.status/testme
issues tostatus/open
orstatus/done
v$RELEASE
for the tag and pick the release/$RELEASE branch. Click theGenerate release notes
button and double check, at the bottom of the release notes, that the commits are across the correct range. For example:https://github.com/NetApp/harvest/compare/v24.05.1...v24.05.2
pbpaste > ghrn_$RELEASE.md
go run pkg/changelog/main.go new
. This will create a file namedreleaseHighlights_$RELEASE.md
. Edit that file to add content (example content)Update Metrics Documentation
docs/ontap-metrics.md
changesThe day of the release
Build with Parameters
and fill in the appropriate fields. Here's an example, whereRELEASE=24.05.2
v$RELEASE
for the tag and pick the release/$RELEASE branch.$RELEASE
in theRelease title
text inputCHANGELOG.md
file, copy the single $RELEASE section at the top, and paste into the release notes text area.Set as the latest release
checkbox is selectedCreate a discussion for this release
checkbox is selectedPublish release
buttongit switch release/$RELEASE
24.05
NOT24.05.2
chore:
prefix