Skip to content

Instantly share code, notes, and snippets.

@vpavlin

vpavlin/release-issue-template.md

Last active July 16, 2020 20:02
Show Gist options
  • Save vpavlin/ed698757fc4670343089c724aade0279 to your computer and use it in GitHub Desktop.
Save vpavlin/ed698757fc4670343089c724aade0279 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
release-issue-template.md

New ODH Release

Version: X.Y.Z

Target date: 1. 1. 1970

Checklist:

  • All issues in the project (link) are in Done
  • A new branch and a tag exist in odh-manifests (link)
  • A new branch and a tag exist in opendatahub-operator (link)
  • PR in the community operators repository is merged (link)
  • Release Notes are added to opendatahub.io (link)
  • Blog post is submitted to developers.redhat.com (link)
@crobby
Copy link

crobby commented Jul 16, 2020

As we go forward, do we plan to tag our set of kf manifests along with each odh relese? They are sort of separate, but as we begin to allow mixing, might there be a benefit to being able to say ODH-manifests X.Y.Z + KF Manifests X.Y.Z are kosher together?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment