Hi Dominik
No, it doesn't. Netstandard 2.0 support is added in addition to the
existing netstandard 1.3 target.
Whilst I'd really like to diminish the target list of the package
(particularly the client profile targets), I'd only be comfortable doing so
on a major version change, and I think that mostly I just want to deprecate
client profiles to enable easier cross-platform dev (those are the only
targets I haven't had joy supporting on Linux so far)
-d
On September 7, 2020 19:55:51 Dominik Psenner <dpsen...@gmail.com> wrote:
Hi
Does this break support for netstandard1.3 and enforces users to update all
their dependants?
Best regards
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Sun, Sep 6, 2020, 21:04 Davyd McColl <dav...@gmail.com> wrote:
Hi all
I'd like to propose a vote to release 2.0.10 of log4net, with:
- updated netstandard 2.0 support from community member NicholasNoise
- cherry-picked fix for CVE-2018-1285 (I had to modify slightly since the
mechanism used there is outdated for netstandard 2.0, but the principle
stands
I've created an RC release at
GitHub: https://github.com/apache/logging-log4net/releases/tag/v2.0.10-rc1 and
pushed updated site material to the `asf-staging` branch of the
logging-log4net-site repo.
Thanks
-d
