DanielLeens commented on issue #11239:
URL: https://github.com/apache/seatunnel/issues/11239#issuecomment-4888298866

   I checked the latest progress here. Since PR #11301 is already open, this 
issue has moved from “feature request” into “implementation under review”.
   
   The current phase-1 boundary still looks right to me: keep the matrix 
intentionally small, prove one or two representative restore paths end to end, 
and make the workflow output clear enough that a failure immediately shows 
which compatibility surface broke.
   
   I would keep this issue open until PR #11301 lands. The broader phase-2 
questions around coverage policy, compatibility contract, and CI budget are 
better tracked separately in #11356 rather than expanded into this first PR.


-- 
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]

Reply via email to