Re: [VOTE] [log4net] Release 2.0.10

2020-09-12 Thread Davyd McColl
Thanks Ralph I want aware I could get the site live like that, but now that I know, I'll lbs better next time. -d On September 12, 2020 20:03:02 Ralph Goers wrote: I checked out the asf-site branch and ran “git rebase asf-staging” and then committed that. The 2.0.10 site is live. Ralph

Re: [VOTE] [log4net] Release 2.0.10

2020-09-12 Thread Ralph Goers
I checked out the asf-site branch and ran “git rebase asf-staging” and then committed that. The 2.0.10 site is live. Ralph > On Sep 12, 2020, at 10:50 AM, Ralph Goers wrote: > > Davyd, > > You have full access to all Logging repos at GitHub. You can publish the > log4net site yourself just

Re: [VOTE] [log4net] Release 2.0.10

2020-09-12 Thread Ralph Goers
Davyd, You have full access to all Logging repos at GitHub. You can publish the log4net site yourself just by committing it to the asf-site branch. The only thing preventing that would be if you want others to review the staged site before you do that. In looking at the log4net site, it reli

Re: [VOTE] [log4net] Release 2.0.10

2020-09-12 Thread Davyd McColl
Thanks Ralph I've pushed the nuget package; links to download artifacts in the site pushed as oy2ky5qgzop2i5hcbgsayxy3rqtvgqnenj2usfjzgansye to asf-staging seem to be fine, tested locally, though I don't see that version of the site up at  https://logging.staged.apache.org/log4net; however, it's

Re: [VOTE] [log4net] Release 2.0.10

2020-09-11 Thread Ralph Goers
The artifacts have been committed to https://dist.apache.org/repos/dist/release/logging/log4net/. Ralph > On Sep 11, 2020, at 9:44 AM, Ralph Goers wrote: > > Davyd, > > That makes 3 +1 PMC votes so you may proceed with the release. Please update > the web site before you publish to NuGet. I

Re: [VOTE] [log4net] Release 2.0.10

2020-09-11 Thread Ralph Goers
Davyd, That makes 3 +1 PMC votes so you may proceed with the release. Please update the web site before you publish to NuGet. I will copy the artifacts to the release distribution area for you. Ralph > On Sep 11, 2020, at 8:19 AM, Dominik Psenner wrote: > > +1 > > -- > Sent from my phone.

Re: [VOTE] [log4net] Release 2.0.10

2020-09-11 Thread Dominik Psenner
+1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Fri, Sep 11, 2020, 08:08 Remko Popma wrote: > +1 > Remko. > > > > (Shameless plug) Every java main() method deserves http://picocli.info > > > On Sep 10, 2020, at 15:24, Davyd McColl wrote: > > > > Hi all >

Re: [VOTE] [log4net] Release 2.0.10

2020-09-10 Thread Remko Popma
+1 Remko. (Shameless plug) Every java main() method deserves http://picocli.info > On Sep 10, 2020, at 15:24, Davyd McColl wrote: > > Hi all > > I realise that I'm causing a bit of a headache by sending mails from my work > account. I'm trying to be more vigilant when sending from my mail

Re: [VOTE] [log4net] Release 2.0.10

2020-09-09 Thread Davyd McColl
Hi all I realise that I'm causing a bit of a headache by sending mails from my work account. I'm trying to be more vigilant when sending from my mail client, but perhaps I need to find a better way, because I just managed to send again from that account this morning, and I understand that may m

Re: [VOTE] [log4net] Release 2.0.10

2020-09-07 Thread Davyd McColl
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

Re: [VOTE] [log4net] Release 2.0.10

2020-09-07 Thread Dominik Psenner
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 wrote: > Hi all > > > I'd like to propose a vote to release 2.0

[VOTE] [log4net] Release 2.0.10

2020-09-06 Thread Davyd McColl
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