In a recent post to the saxon-help mailing list Michael Kay announced:
I've issued a maintenance release that contains fixes for all the bugs reported on 8.5.It also includes some enhancements relating to multiple modules in XQuery,
and some performance improvements dealing with the parsing of large numbers
of small files, and reducing contention on the shared NamePool. Thanks to
those who contributed the insights that led to these improvements.Michael Kay
I will merge the changes into the Saxon.NET CVS repository later this afternoon and if it doesn't seem like much more than a rebuild of the Java source to then be processed by IKVM.NET I will do just that and check the resulting debug (dll, exe's, and pdb's) and release (dll, exe's, all of which will be signed) files in as well.
Please note: I plan to make this standard policy if Dr. Kay releases any new Saxon bits over the next few months -- meaning merging the source, running a build process, testing for issues that are easily detectable; if all looks Ok at this level I will check the resulting debug and release files into CVS, using this as the "official" release mechanism until such time as I have completed and integrated an NUnit test suite.
At that point (development and integration of an NUnit test suite) it can be verified if Saxon.NET passes all conformance test's based on the latest available specification; if yes, I will package up an .msi and release this publicly; if no, then this will give me a good place to begin hacking out the now known issues.