Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release v0.5.0 #158

Closed
27 of 31 tasks
ArangoGutierrez opened this issue May 17, 2022 · 9 comments
Closed
27 of 31 tasks

Release v0.5.0 #158

ArangoGutierrez opened this issue May 17, 2022 · 9 comments
Assignees
@marquiz @zvonkok @ArangoGutierrez
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@ArangoGutierrez
Copy link
Contributor

ArangoGutierrez commented May 17, 2022 •
edited
Loading

Release Checklist

  • All OWNERS must LGTM the release proposal
  • Verify that the changelog in this issue is up-to-date
  • For major releases (v0.$MAJ.0), an OWNER creates a release branch
    • An OWNER creates a vanilla release branch from master
      git branch release-0.$MAJ master
    • An OWNER pushes the newly created branch
      git push release-0.$MAJ
  • Update references in docs/_config.yml (version, release and container_image fields) to point to the upcoming release and subbmit a PR against the release branch
  • An OWNER creates an annotated and signed tag with
    git tag -a -s $VERSION
    and inserts the changelog into the tag description.
  • An OWNER pushes the tag with
    git push $VERSION
    This will trigger prow to build and publish a staging container image
    gcr.io/k8s-staging-nfd/node-feature-discovery-operator:$VERSION
  • Submit a PR against k8s.io, updating k8s.gcr.io/images/k8s-staging-nfd/images.yaml to promote the container image to production
  • Wait for the PR to be merged and verify that the image (k8s.gcr.io/nfd/node-feature-discovery-operator:$VERSION) is available.
  • Write the change log into the Github release info.
  • Add a link to the tagged release in this issue.
  • Create a new bundle for the $VERSION release at https://github.com/k8s-operatorhub/community-operators
  • Send an announcement email to kubernetes-dev@googlegroups.com with the subject [ANNOUNCE] node-feature-discovery-operator $VERSION is released
  • Add a link to the release announcement in this issue
  • Close this issue

Changelog
@ArangoGutierrez
Copy link
Contributor Author

https://github.com/kubernetes-sigs/node-feature-discovery-operator/milestone/2

@ArangoGutierrez ArangoGutierrez added the sig/release Categorizes an issue or PR as relevant to SIG Release. label May 17, 2022
@ArangoGutierrez ArangoGutierrez modified the milestone: v0.5.0 May 17, 2022
@ArangoGutierrez ArangoGutierrez added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 17, 2022
@ArangoGutierrez
Copy link
Contributor Author

#159

@ArangoGutierrez
Copy link
Contributor Author

https://github.com/kubernetes-sigs/node-feature-discovery-operator/releases/tag/v0.5.0

@ArangoGutierrez
Copy link
Contributor Author 

[eduardo@fedora-workstation node-feature-discovery-operator]$ skopeo list-tags docker://gcr.io/k8s-staging-nfd/node-feature-discovery-operator |grep v0.5
        "v0.5.0",
        "v0.5.0-minimal"

@ArangoGutierrez
Copy link
Contributor Author

kubernetes/k8s.io#3806

@ArangoGutierrez
Copy link
Contributor Author 

[eduardo@fedora-workstation node-feature-discovery-operator]$ skopeo list-tags docker://k8s.gcr.io/nfd/node-feature-discovery-operator
{
    "Repository": "k8s.gcr.io/nfd/node-feature-discovery-operator",
    "Tags": [
        "sha256-1df0772902d482a3b37bb191ba02def1303036cd20caf042db8e449aaadf2e62.sig",
        "sha256-872c252c5f1eabdae10472a2a7bf5d492a8559af3301896b1fae85edb51b7c92.sig",
        "sha256-931084eeb0bd1f4f424a965c38999e2905295e1ad228390af6f4962b6a4b788c.sig",
        "sha256-e6ac896f0bf38e362d256f35a8d2ced6086a706321e1e9b7d842e4877c242f67.sig",
        "v0.2.0",
        "v0.3.0",
        "v0.3.0-minimal",
        "v0.4.0",
        "v0.4.0-minimal",
        "v0.4.1",
        "v0.4.1-minimal",
        "v0.4.2",
        "v0.4.2-minimal",
        "v0.4.3",
        "v0.4.3-minimal",
        "v0.5.0",
        "v0.5.0-minimal"
    ]
}

@ArangoGutierrez
Copy link
Contributor Author

https://github.com/kubernetes-sigs/node-feature-discovery-operator/releases/tag/v0.5.0

@ArangoGutierrez
Copy link
Contributor Author

k8s-operatorhub/community-operators#1311

@ArangoGutierrez
Copy link
Contributor Author

https://groups.google.com/a/kubernetes.io/g/dev/c/aApaz7Dqpps

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

@marquiz marquiz

@zvonkok zvonkok

@ArangoGutierrez ArangoGutierrez

Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@marquiz @zvonkok @ArangoGutierrez