stevedlawrence commented on PR #987:
URL: https://github.com/apache/daffodil/pull/987#issuecomment-2648903321

   Might want to hold off until all the 2.13 changes are in since that's kindof 
touching everything and might make dealing with merge conflicts difficult?
   
   Also, breaking backwards compatibility in 4.0.0 is less of a concern than 
usualy, but we should still have backwards compatibility notes, especially 
explaining how to update schemas that relied on the old behavior. Did you ever 
come up with a generic way to update schemas to work with this change? I 
thought one of the issues preventing merging in 3.10 was there wasn't really a 
good way to do that?


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