Github user chlowell commented on the issue:
https://github.com/apache/logging-log4net/pull/14
Glad the build works. I expect CI will be blocked until there's some
resolution for nunit/nunit3-vs-adapter#377, and I suppose there's also a
decision to make about the exclusive locking test. The failure isn't a
regression from `netstandard1.3` but I'd like at least to get clearer about the
root cause. I probably won't have time to get deeper into it until late next
week.
Since you've merged this code into a feature branch, I think we can close
this PR, and I'll base anything further on that branch. Do we need an issue
somewhere to track work needed before a release supporting `netstandard2.0`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
