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
Thorsten, do all of the tests pass for you? The reason I ask is because
the 'encodingtest' always fails for me. I've gotten the build to run with
Github Actions as well, and it always fails there as well, so maybe there's
some sort of locale/encoding issue going on?
One of the tests currently fa
Hi Matt
In that case, I can create an -rc1 release on GitHub; when everyone is happy, I
can upload the accepted binaries to SVN so as not to upload too much junk (:
I'll start a vote now (:
Thanks again for your help
-d
On 2020/09/06 20:43:16, Matt Sicker wrote:
I don't think we've ever used
I don't think we've ever used the GitHub Releases feature here before,
though draft releases appear to be limited to being seen only by those
with write access to that. For making a release candidate, you'd
essentially be making a release for version X but adding -rc1 (or
-rc2, etc.) to the tag nam
Thanks Matt
I was trying to use GitHub's release feature to create a draft release to
present binaries including signing and hashing, and needed a tag to work
against; however, I think that this process won't work anyway, because I'm not
100% sure on the visibility of a draft release. I've dele
It's not a good idea to use rel/ tags until after a release vote since
those tags are immutable. If you want to put them in rel/, they'll
need an -rc1 type suffix to distinguish from the resulting release.
On Sun, 6 Sep 2020 at 13:10, wrote:
>
> This is an automated email from the ASF dual-hosted
