Github user chlowell commented on the issue:
https://github.com/apache/log4net/pull/16
@bodewig I chose the version number to prevent any confusion between
prerelease and published packages. There's no reason not to change it before
release.
I chose `netstandard1.3` because it's the lowest version with the required
APIs. Targeting a higher version than necessary generally brings no benefit.
For example, UAP 10.0 (the current version) supports `netstandard1.4`. If
log4net targets `netstandard1.6`, UWP apps won't be able to use it (at least,
not without a hack). There's more on this in the
[docs](https://docs.microsoft.com/en-us/dotnet/articles/standard/library#net-platforms-support).
There's no need to worry about overriding--a project targeting .NET
Framework 4.5 or below won't use the `netstandard1.3` assembly.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
