[DISCUSS] Deprecation and removal of the legac
Last call for feedback on this topic.
It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been accepted for a very long time, I think we don't need another voting thread for executing the last implementation step. Please let me know if you think differently.
I will start deprecating the affected classes and interfaces beginning of next week.*来自志愿者整理的flink邮件归档
版权声明：本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
The message you've shared appears to be related to the development process within the Apache Flink community, specifically referencing a FLIP (Flink Improvement Proposal). FLIP-32 is a proposal for improving or modifying the Flink framework. These proposals go through multiple stages, including discussion, review, acceptance, and implementation.
When the message mentions "last call for feedback," it's an invitation for final comments or concerns from the community before proceeding with the next steps of the FLIP. The statement that everyone seems to agree on completing FLIP-32 suggests there's consensus around implementing the changes proposed in this document.
The mention of not needing another voting thread implies that previous discussions or votes have already established agreement on the direction, and the speaker believes they can move forward with the implementation without further formal voting.
Deprecating classes and interfaces means marking them as outdated or discouraged for future use, typically because they are being replaced by better alternatives or their functionality is being integrated elsewhere in a more efficient manner. Starting this process at the beginning of the next week indicates a clear timeline for moving forward with the FLIP's execution.
In the context of Alibaba Cloud products and services, if you're looking for ways to manage or automate similar processes in your own development workflow, you might consider using tools like:
-
Alibaba Cloud DevOps: A platform that provides a series of DevOps services to help teams collaborate and automate software delivery, from code to deployment.
-
Function Compute: If parts of your workflow involve executing small pieces of code in response to events, Function Compute can be used to automate tasks, which could include triggering deprecation notices or managing version updates.
-
OSS (Object Storage Service): For storing and managing large amounts of data, including logs and archives related to your project's evolution and decision-making processes.
-
ActionTrail: To track and retain records of actions taken in your Alibaba Cloud account, which can be useful for auditing changes made during the implementation of such improvement proposals.
Remember, while these tools can facilitate and streamline your development and operations流程, the specific application would depend on the details of your project and how FLIP-like improvements integrate into your workflow.
