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.

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

Prepare for releasing v0.4.0 #544

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

tenzen-y
Copy link
Member

@tenzen-y tenzen-y commented Apr 4, 2023

Mainly, I updated the release note.

Note: Blocked on #540 #543.

/assign @alculquicondor @terrytangyuan

RELEASE.md Show resolved Hide resolved
@alculquicondor
Copy link
Collaborator

/hold
(to merge at the right time)

@tenzen-y tenzen-y changed the title WIP: Prepare for releasing v0.4.0 Prepare for releasing v0.4.0 Apr 4, 2023
Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

/lgtm

@google-oss-prow google-oss-prow bot added the lgtm label Apr 4, 2023
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan

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:

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

RELEASE.md Show resolved Hide resolved
RELEASE.md Outdated Show resolved Hide resolved
RELEASE.md Show resolved Hide resolved
RELEASE.md Outdated Show resolved Hide resolved
@alculquicondor
Copy link
Collaborator

/lgtm

@google-oss-prow google-oss-prow bot added the lgtm label Apr 4, 2023
@tenzen-y
Copy link
Member Author

tenzen-y commented Apr 5, 2023

@alculquicondor Once #545 is merged into the master branch, can we merge this PR?

@alculquicondor
Copy link
Collaborator

Let me try to upload the images first.

@tenzen-y
Copy link
Member Author

tenzen-y commented Apr 5, 2023

Let me try to upload the images first.

Sure.

@tenzen-y
Copy link
Member Author

tenzen-y commented Apr 5, 2023

Oh, conflicts are happening.

Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
@tenzen-y
Copy link
Member Author

tenzen-y commented Apr 5, 2023

Oh, conflicts are happening.

Resolved.

@@ -17,7 +17,7 @@ REPO_PATH="github.com/kubeflow/mpi-operator"
REL_OSARCH="linux/amd64"
GitSHA=$(shell git rev-parse HEAD)
Date=$(shell date "+%Y-%m-%d %H:%M:%S")
RELEASE_VERSION?=v0.3.0
RELEASE_VERSION?=v0.4.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, we used 0.3.0 in the tag before, as opposed to v0.3.0

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upon confirmation, only v0.2.3 has a v prefix.

@alculquicondor
Copy link
Collaborator

/lgtm

we can merge this right after the release is published in github

@google-oss-prow google-oss-prow bot added the lgtm label Apr 5, 2023
@alculquicondor
Copy link
Collaborator

or actually, before should be good

/hold cancel

@tenzen-y
Copy link
Member Author

tenzen-y commented Apr 5, 2023

or actually, before should be good

Previously (v0.3.0), we merged before cutting a new release.

https://github.com/kubeflow/mpi-operator/commits/v0.3.0

@google-oss-prow google-oss-prow bot merged commit 1269e88 into kubeflow:master Apr 5, 2023
@tenzen-y tenzen-y deleted the update-rlease-0.4 branch April 5, 2023 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants