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

[WIP][Feature] Support Flink 1.20 application submit #3976

Open
2 of 3 tasks
muchunjin opened this issue Aug 20, 2024 · 6 comments
Open
2 of 3 tasks

[WIP][Feature] Support Flink 1.20 application submit #3976

muchunjin opened this issue Aug 20, 2024 · 6 comments

Comments

@muchunjin
Copy link
Contributor

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

Support Flink 1.20 application submit

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@muchunjin
Copy link
Contributor Author

@lizh501 I hope you can contribute this feature.

@lizh501
Copy link

lizh501 commented Aug 20, 2024

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

@muchunjin
Copy link
Contributor Author

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

After 2.1.5 is released, the release-2.1.5 code branch will be generated. The dev-2.1.6 branch will be pulled from release-2.1.5, and then development will be carried out based on dev-2.1.6.

@muchunjin
Copy link
Contributor Author

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

After 2.1.5 is released, the release-2.1.5 code branch will be generated. The dev-2.1.6 branch will be pulled from release-2.1.5, and then development will be carried out based on dev-2.1.6.

After completing this work, merge it into dev-2.1.6 and dev branches.

@lizh501
Copy link

lizh501 commented Aug 21, 2024

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

After 2.1.5 is released, the release-2.1.5 code branch will be generated. The dev-2.1.6 branch will be pulled from release-2.1.5, and then development will be carried out based on dev-2.1.6.

Roger that.

@lizh501
Copy link

lizh501 commented Aug 21, 2024

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

@lizh501 I hope you can contribute this feature.

I am glad to do it. Thank you.

After 2.1.5 is released, the release-2.1.5 code branch will be generated. The dev-2.1.6 branch will be pulled from release-2.1.5, and then development will be carried out based on dev-2.1.6.

After completing this work, merge it into dev-2.1.6 and dev branches.

OK, I will follow.

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

No branches or pull requests

2 participants