mukulga commented on PR #1: URL: https://github.com/apache/xalan-test/pull/1#issuecomment-1546514081
> Before deciding what to do with each of these, we should really make sure that running it on at least one other platform (eg Windows) produces the same results. But as far as Linux is concerned, the two which are confirmed to be genuine glitches are 1251 and 1266, and I have documented the apparent causes and proposed fixes for both. > > That gets rid of a lot of suspected technical debt! > > Once we have consensus on these, it would be nice to burn down the Jira backlog too. > > That would leave us with a clean (as far as we know) implementation of Xalan 2, which would be better for the users and a more stable base for further work. I agree with you. I'm personally interested to, try XalanJ implementation testing (on windows perhaps to start with) with the improvements provided by this PR. I think, we should merge this PR to the asked xalan-test destination branch (i.e, 'master'). Then we could take a pull of new contents (which shall have improvements provided by this PR) of xalan-test 'master' branch, and do local testing of XalanJ implementation with tests provided by xalan-test repo's branch 'master'. I hope that, @garydgregory shall find time at his earliest convenience, to merge this 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: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
