release: add a small script to "automate" bugfix releases

[vdemeester]

Changes

Adding a bugfix-release.sh script to automate bugfix releases. Today
it is meant to be started by a maintainer, like the following

./tekton/bugfix-release upstream/release-v0.47.x

• It will detect the old version, and commit related to the version
• It will compute the new version number
• It will detect the release name
• If there is no different between the old version and the new
  one (aka, no commit in the release branch since last release), it
  will be exit gracefully.

The idea is that, from there, we can automate the bugfix release
completely. We could run this script weekly for each "supported"
release branch, and it would automatically do the release for us.

Signed-off-by: Vincent Demeester vdemeest@redhat.com

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[vdemeester]

cc @afrittoli @chitrangpatel @JeromeJu
"Perfect is the enemy of good" 😛 I wrote that script this afternoon to "ease my pain" of doing 4 bugfix releases — it's not perfect but it should be a good starting point.

[JeromeJu]

Thanks @vdemeester 🤖 🚀

[vdemeester]

/test check-pr-has-kind-label

[tekton-robot]

@vdemeester: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-tekton-pipeline-alpha-integration-tests
• /test pull-tekton-pipeline-beta-integration-tests
• /test pull-tekton-pipeline-build-tests
• /test pull-tekton-pipeline-integration-tests
• /test pull-tekton-pipeline-unit-tests

The following commands are available to trigger optional jobs:

• /test pull-tekton-pipeline-go-coverage

Use /test all to run all jobs.

In response to this:

/test check-pr-has-kind-label

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JeromeJu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JeromeJu]

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

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JeromeJu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JeromeJu]

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

[chitrangpatel]

/lgtm