-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.5 preparation #11381
Comments
Archived workflows related issues (@toyamagu-2021 WDYT?):
CronWorkflow issues (any plans on fixing them before the release? @juliev0): |
Agree with Archived workflow-related issues! |
Per discussions from today's meeting, CronWorkflow related issues are low priority and not blockers for this release. |
Hi! |
Yes everything on master branch will be included. |
Here's the draft release blog: https://medium.com/@terrytangyuan/whats-new-in-argo-workflows-v3-5-f260e8603ca6 Any feedback would be appreciated! Let me know if there's anything else worth highlighting. |
Tagged and started release process: https://github.com/argoproj/argo-workflows/releases/tag/v3.5.0-rc1 |
Let's leave this open to track bug fixes that should be included before v3.5.0 GA. |
Candidates to include in next RC releases: |
Per discussions in today's contributors meeting, we'll include everything from master branch for release candidates. I will release RC2 this week. |
Published tag: https://github.com/argoproj/argo-workflows/releases/tag/v3.5.0-rc2 The release blog has also been updated to include the new features. Let me know if I have missed anything though. https://blog.argoproj.io/whats-new-in-argo-workflows-v3-5-f260e8603ca6 |
I'll be publishing v3.5.0 by the end of this week. |
@terrytangyuan ping me when the final PR for this has been accepted, I will open a new PR with the updated Nix hash. |
@isubasinghe Which final PR are you referring to? |
|
We will release everything on the master branch.
There might be outstanding high-priority issues we'd like to address before v3.5 release. Let's use this issue to track and discuss.
The text was updated successfully, but these errors were encountered: