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

Release v3.4.6 cherry-pick candidates #10747

Closed
27 of 33 tasks
terrytangyuan opened this issue Mar 24, 2023 · 13 comments
Closed
27 of 33 tasks

Release v3.4.6 cherry-pick candidates #10747

terrytangyuan opened this issue Mar 24, 2023 · 13 comments
Assignees
Labels
type/feature Feature request

Comments

@terrytangyuan
Copy link
Member

terrytangyuan commented Mar 24, 2023

Hi community, here's the a list of commits that can potentially go to the v3.4.6 Argo Workflows release that we are preparing. If you have additional commits/issues/PRs that you want to bring attention to the maintainers, please comment on this issue!

Bug fixes

CI and build fixes that might fix/improve the CI during release:

@terrytangyuan terrytangyuan added the type/feature Feature request label Mar 24, 2023
@tooptoop4
Copy link
Contributor

@terrytangyuan #9058 is also important

@sarabala1979
Copy link
Member

Thanks, @terrytangyuan for creating this release issue. We will schedule 3.4.6 on Friday.

@terrytangyuan
Copy link
Member Author

Thanks, @terrytangyuan for creating this release issue. We will schedule 3.4.6 on Friday.

Sounds good. I can follow the release instructions and start cherry-picking the commits to release-3.4 branch. Is that okay? Is there anything else I should pay attention to during the process? @sarabala1979 @alexec

@terrytangyuan
Copy link
Member Author

@terrytangyuan #9058 is also important

Looks like it's still in draft cc @rohankmr414 @caelan-io @JPZ13

@caelan-io
Copy link
Member

yeah, #9058 isn't quite ready. 1-2 hairy problems to resolve there. @rohankmr414 will post once it's ready to merge.

@sarabala1979
Copy link
Member

Thanks, @terrytangyuan for creating this release issue. We will schedule 3.4.6 on Friday.

Sounds good. I can follow the release instructions and start cherry-picking the commits to release-3.4 branch. Is that okay? Is there anything else I should pay attention to during the process? @sarabala1979 @alexec
Yes,

we can take entire master(all fixes) to current v3.4.6. I think there won't be any breaking changes

@terrytangyuan
Copy link
Member Author

Yes, all fixes are listed in the issue description. I'll tag a release on Friday.

Please feel free to comment if there are any additional fixes that you'd like to bring into this release.

@terrytangyuan
Copy link
Member Author

This needs to be included since we copy ssh_known_hosts in our Dockerfiles:

@tico24
Copy link
Member

tico24 commented Mar 30, 2023

We'd like to get #10745 in please @terrytangyuan.

@terrytangyuan
Copy link
Member Author

We'd like to get #10745 in please @terrytangyuan.

We only cherry-pick fixes, not features, into patch releases.

@terrytangyuan
Copy link
Member Author

terrytangyuan commented Mar 30, 2023

The release branch is ready (note that certain commits are not cherry-picked, either unnecessary or due to too many conflicts to resolve). It passed CI checks as well as a dry-run for release.

https://github.com/argoproj/argo-workflows/tree/release-3.4

I'll create a tag tomorrow to kick off the release.

@terrytangyuan
Copy link
Member Author

@terrytangyuan terrytangyuan self-assigned this Apr 10, 2023
@tooptoop4
Copy link
Contributor

yeah, #9058 isn't quite ready. 1-2 hairy problems to resolve there. @rohankmr414 will post once it's ready to merge.

@caelan-io any update on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature Feature request
Projects
None yet
Development

No branches or pull requests

5 participants