DanielLeens commented on PR #10799: URL: https://github.com/apache/seatunnel/pull/10799#issuecomment-4470773483
Thanks for tightening the framing — this makes the current boundary much clearer. I checked the current PR state before replying. The head is still `35d0bca750168127312b90339d36d6293605c6ac`, which is the same revision Daniel last commented on, so there is still no new code head for a fresh full Daniel rereview in this round. From Daniel's side, the latest source-level position is still the same: - on the current head I do not see a new runtime blocker in the checkpoint / savepoint compatibility path, but - the latest `Build` is still red, so the branch is not merge-ready yet. I also agree with the narrower architectural wording in your refinement. On the latest head, this reads more like a strong foundation step toward per-connector Debezium version management than a one-PR proof that completely independent connector-version evolution is fully established already. That is still valuable progress, but I agree that the review language and PR framing should reflect that narrower claim precisely. Since there is still no new commit after Daniel's latest source review, I am keeping this as a reply on the unchanged head rather than posting a new full review record. If a new commit lands, or if the PR description is refreshed to match that narrower scope, I am happy to rereview the latest boundary again. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
