> @Leonard > If we follow the agreed-upon and voted path and do not revert [1], all the > formalities get fulfilled
Hi Alexander Sorry for making you uncomfortable even though it was discussed on the dev list and under JIRA before reverting this PR. I'm also +1 for the FLIP as your posted. The reason to revert the PR is not -1 for the voted FLIP, the reason we revert the PR is the incorrect subtask implementation order. We should not mark the API as deprecated firstly and then to implement the necessary subtasks. In this way, the user will see the deprecated API firstly but they can not find a candidate if we can not finish all tasks in one minor version . In this case, there're 7 subtasks to resolve and only 3 days left for 1.18 feature freeze, that means we have a high probability of releasing a deprecated API but not providing a migration path. It looks like that we voted a FLIP for a feature Flink supports XXX, we first add this feature to the document to tell users that Flink supports t XXX, but this feature may needs many subtasks to be completed in one or more versions. So, before we actually support XXX, it is incorrect for users to see this document that Flink supports XXX, we should add the document after we have finished all subtasks of the voted feature. Please correct me if I wrongly understand the order of sub-task. Best, Leonard > >> Hi Alexander >> >>> I see your concerns regarding the complexity of migration, but we still >>> have one year to address them. >> >> Not only the complexity of migration, but also we lack migration path for >> now. We have to deprecate SourceFunction/SinkFunction in 1.18 which feature >> freeze date is 2023/07/24 CEST If we want to remove >> SourceFunction/SinkFunction in 2.0, remove a public API requires at least >> two minor versions. There’re many subtasks to finish before we can mark >> them as deprecated[1], I think we have no time to finish these subtasks >> this week(hint: not this year). That’s why we suggested removing the >> SourceFunction/SinkFunction item from must to have. >> >> Best, >> Leonard >> [1]https://issues.apache.org/jira/browse/FLINK-28045 >> >>
