sig-storage-local-static-provisioner icon indicating copy to clipboard operation
sig-storage-local-static-provisioner copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Changelog for 2.6.0

Open mauriciopoppe opened this issue 3 years ago • 5 comments

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind documentation

What this PR does / why we need it: CHANGELOG for 2.6.0, generated with the instructions in RELEASE.md from https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/pull/299

Release note:

NONE

/hold Waiting for other changes to be merged, I'll keep the new file up to date https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/pull/299

mauriciopoppe avatar Mar 28 '22 22:03 mauriciopoppe

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mauriciopoppe To complete the pull request process, please assign wongma7 after the PR has been reviewed. You can assign the PR to them by writing /assign @wongma7 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

k8s-ci-robot avatar Mar 28 '22 22:03 k8s-ci-robot

/uncc @saad-ali @wongma7

mauriciopoppe avatar Mar 28 '22 22:03 mauriciopoppe

@mauriciopoppe shall we publish a release for 2.5.0 now? current latest release is v2.4.0, so it should be v2.5.0 release. Let me know what I could help, thanks.

andyzhangx avatar Jul 07 '22 07:07 andyzhangx

yes, I think somewhere in the dev process I made a mistake and pushed the helm chart with v2.5.0, anyways I think we could match the helm version with the repo version and have v2.6.0 for the next release

mauriciopoppe avatar Jul 07 '22 18:07 mauriciopoppe

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Oct 08 '22 10:10 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Nov 07 '22 11:11 k8s-triage-robot

I'll create a new one instead.

mauriciopoppe avatar Nov 07 '22 17:11 mauriciopoppe