Closed muchunjin closed 6 days ago
@lizh501 I hope you can contribute this feature.
@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.
@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.
@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 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 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.
done
Search before asking
Description
Support Flink 1.20 application submit
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct