Re: [VOTE] Release Apache Log4net 3.0.1

+1 - tests all pass - sigs look fine -d On 2024-09-24 21:48, Jan Friedrich wrote: This is a vote to release the Apache Log4net 3.0.1. Website: https://logging.staged.apache.org/log4net/release/release-notes.html GitHub: https://github.com/apache/logging-log4net GitHub release (pre-release):

Re: [VOTE] Release Apache Log4net 3.0.0

Hi Apologies for the late response. FWIW, my +1 too. -d On 15 September 2024 20:59:13 Jan Friedrich wrote: Hi, and here is my +1. With that the vote passed with 3 +1 votes from Piotr P. Karwasz, Volkan Yazıcı and myself. I will continue the release process. Jan Friday, September 13, 2

Re: [log4net] INFRA-managed NuGet account

I've accepted; delete the other org at your convenience. -d On 2024-09-02 11:39, Volkan Yazıcı wrote: I have succeeded in convincing INFRA to create a NuGet organization (INFRA-25617)  that we can move our .NET projects to. As a result, INFRA

[RESULT] [VOTE] Release Apache Log4Net 2.0.17

at 1:29 PM Davyd McColl wrote: Hi all, This is a vote to release the Apache Log4net 2.0.17. Website: https://logging.staged.apache.org/log4net/release/release-notes.html GitHub: https://github.com/apache/logging-log4net GitHub release (pre-release): https://github.com/apache/logging-log4net/rel

Re: [VOTE] Release Apache Log4Net 2.0.17

ld run-s clean-build log4net@2.0.12 clean-build rimraf build log4net@2.0.12 build zarro @ Why does it say log4net@2.0.12 when I am building 2.0.17? Then the build errors out with https://paste.apache.org/1ropz I, off course, don't know what I'm doing with .net... ;-) Gary On 2024/03/1

[VOTE] Release Apache Log4Net 2.0.17

Hi all, This is a vote to release the Apache Log4net 2.0.17. Website: https://logging.staged.apache.org/log4net/release/release-notes.html GitHub: https://github.com/apache/logging-log4net GitHub release (pre-release): https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1 Dis

Re: [VOTE] Release Apache Log4net 2.0.16

d the messages already from your email app, go to lists.apache.org Gary On Fri, Mar 8, 2024, 8:59 AM Davyd McColl wrote: Hi Gary I'll try to remember that for the future. From memory now, there was only one person who had any holdups and that was due to outdated build docs from me - so it

Re: [VOTE] Release Apache Log4net 2.0.16

next time. -d On 2024/03/08 14:22, Gary Gregory wrote: Process: You need to reply to this thread with a [RESULT] prefix, tally all the votes, and say whether the vote passes or not. It is helpful to note which votes are binding or not. Gary On Fri, Mar 8, 2024, 6:06 AM Davyd McColl wrote:

Re: [VOTE] Release Apache Log4net 2.0.16

copyright year, but I don't find it a blocker. (I have fixed it in `master`.) On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote: Hi all This is the vote to release Apache log4net version 2.0.16 Website: https://logging.staged.apache.org/log4net/release/release-notes.html GitHub: https://

Re: [VOTE] Release Apache Log4net 2.0.16

e successful. > > We integrated the new version into our test environment and all manual tests were successful. > > > > Jan > > > >> +1 > > > >> Verified signatures. > >> Verified hashes. > > > >> `NOTICE` contains 2022 as the

Re: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

s://stackoverflow.com/questions/2341134/command-line-svn-for-windows> Let me know if this does/doesn't help. Good luck! On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl wrote:     Hi Volkan     That was my whole point with the question on my release vote: I     have put things in svn, bit I'

Re: Uploading release distribution for review (Was: [VOTE] Release Apache Log4net 2.0.16)

.com/questions/2341134/command-line-svn-for-windows> Let me know if this does/doesn't help. Good luck! On Fri, Mar 1, 2024 at 5:02 PM Davyd McColl wrote: Hi Volkan That was my whole point with the question on my release vote: I have put things in svn, bit I'm not seei

Re: [VOTE] Release Apache Log4net 2.0.16

stribution to the ` https://dist.apache.org/repos/dist/dev/logging /log4net` Subversion folder along with checksum and signature files, please? On Fri, Mar 1, 2024 at 2:19 PM Davyd McColl wrote: Hi all This is the vote to release Apache log4net version 2.0.16 Website: https://logging.staged.a

[VOTE] Release Apache Log4net 2.0.16

Hi all This is the vote to release Apache log4net version 2.0.16 Website: https://logging.staged.apache.org/log4net/release/release-notes.html GitHub: https://github.com/apache/logging-log4net GitHub release (pre-release): https://github.com/apache/logging-log4net/releases/tag/2.0.16-rc1

Re: [log4net] Next release

te: Hi Davyd, On Thu, 29 Feb 2024 at 12:29, Davyd McColl wrote: Jan, Volkan brings up one of the sticky points - signing the release - which I can do from my personal machine, with the binary artifacts in place - so I could do steps 3 and 4 (build and sign) - but I'll only This is jus

Re: [log4net] Next release

ou can intervene (e.g., signing artifacts, uploading to SVN) whenever needed. If you say this will make things more difficult, that is also understandable. On Thu, Feb 29, 2024 at 11:01 AM Davyd McColl wrote: Considering my constrained time, and even though @FreeAndNil <https://github.com/

Fwd:

Apologies, I responded directly to Volkan instead of the list ): -d Forwarded Message Subject:Re: Date: Tue, 13 Feb 2024 12:00:05 +0200 From: Davyd McColl To: Volkan Yazıcı I'd really like to chuck JIRA in a lake of fire and watch it burn slowly /2

Re: New committer: Fred am Nil (`freeandnil`)

Welcome Fred! -d On 09 February 2024 21:54:45 Fred am Nil wrote: Hello, thank you very much for the warm welcome. I'm looking forward to collaborating with everyone and making meaningful contributions to the Apache Logging Services projects. Best regards. Jan PPK> Welcome, Jan! PPK> O

Re: log4net maintainers

Hi That would be great! I'd really appreciate the help, and I've obviously seen your prior contributions (: There is a process to follow, so we'll get that started and get back to you (: -d On 2024/01/31 13:01, Fred am Nil wrote: Hi, as proposed by Volkan Yazıcı in https://github.com/a

Re: [log4net] Project state

ease? On Wed, Nov 1, 2023 at 1:20 PM Davyd McColl wrote: Hi Yes, I'd agree that log4net is "at risk" seeing as I'm apparently the only active maintainer - and I'm not even that active, having not found time in quite a while to do some log4net work )

Re: Docs?

Ralph, I'd appreciate any help here. Seems there's a permissions error or something - sdk docs links return a 403. -d On 16 November 2022 23:22:26 Alex Winfield <7nil...@gmail.com> wrote: Where should I look for the docs? All of the examples point to dead links: https://logging.apache.org/

Re: log4net 2.0.15 vote

Hi all Thanks for the votes, 2.0.15 is now live. -d On Aug 4 2022, at 5:14 am, Davyd McColl wrote: > > Hi Ralph > Yes, I'll release as soon as I get a gap. I replied to the signing request > too - not sure what happened to 2.0.14, but every other release is signed. > The s

Re: log4net 2.0.15 vote

nothing about .net development. -Robert Middleton On Mon, Jul 25, 2022 at 5:45 AM Davyd McColl wrote: Hi all It's been a while, but I've finally tied together some work in a 2.0.15 release for log4net. An rc tag is up at GitHub with details: https://github.com/apache/logging-log4ne

Re: [VOTE] Release log4net 2.0.15

elease is done via this vote. > >> > >> I'll take a look at it in a bit just to validate that the signatures > >> are good, as I know nothing about .net development. > >> > >> -Robert Middleton > >> > >> On Mon, Jul 25, 2022 at 5:45 AM

Re: [VOTE] Release log4net 2.0.15

t; >> I'll take a look at it in a bit just to validate that the signatures > >> are good, as I know nothing about .net development. > >> > >> -Robert Middleton > >> > >> On Mon, Jul 25, 2022 at 5:45 AM Davyd McColl > >> wrote: > >

[VOTE] Release log4net 2.0.15

Hi all It's been a while, but I've finally tied together some work in a 2.0.15 release for log4net. An rc tag is up at GitHub with details: https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.15-rc1 I've pushed docs to staging as well as binaries to https://dist.apache.org/repos/dis

Re: EventLogAppender is missing in .NET (not Framework)

Hi Vladimir Yes, you're correct that the event log appender isn't available in the netstandard version of log4net because it's not cross-platform. Right now, I don't have capacity to build one (I have outstanding work I'd like to do in log4net as it is), so the best suggestions I can give are: I

Re: Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

answer to the current thread in the mailing list, rather than creating a new thread on each response? Thank you guys Denis From: Davyd McColl mailto:dav...@gmail.com]> Sent: Tuesday, February 22, 2022 3:29 PM To: dev@logging.apache.org [mailto:dev@logging.apache.org] Cc: Petker Denis 8

Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

ggingEvent > class > > I guess. So the username would then be provided to LoggingEvent objects > > from whatever is creating them? > > > > > > -Original Message- > > From: Davyd McColl > > Sent: Monday, February 21, 2022 6:43 PM > > To: dev@log

RE: [Newsletter] [Newsletter] Re: log4net - performance hit because UserName is fetched always

/ Company's Place of Business: München, Registereintrag / Commercial Register No.: HRB 7 534, Umsatzsteuer-Identifikationsnummer (USt-IdNr.) / VAT Identification No.: DE 130 256 683, Elektro-Altgeräte Register (EAR) / WEEE Register No.: DE 240 437 86 From: Davyd McColl Sent: Tuesday, Februa

RE: [Newsletter] Re: log4net - performance hit because UserName is fetched always

p and cache for the remaining runtime? In order to be backward compatible, we then still need to maintain the UserName property in the LoggingEvent class I guess. So the username would then be provided to LoggingEvent objects from whatever is creating them? -Original Message- From: Davyd

Re: log4net - performance hit because UserName is fetched always

Hi Denis Thanks for the report (: I'm happy to review contributions, though for this particular issue, it seems like the resolution is to cache the resolved user name, rather than allowing specifying the name via config. The whole point of this property is to log the username under which the pr

Re: [VOTE] Future of Log4j 1.x

+1, option 1 Apologies for the delay, took me a while to find the original email. -d On December 29, 2021 21:33:35 "Christian Grobmeier" wrote: Hello, as discussed in another thread, this is a vote about the future of log4j 1. This vote stays open for the usual 72h. Options are explain

Re: [DISCUSS] Starting social media accounts for subprojects

+1 for accounts per project -d On December 31, 2021 01:02:08 Remko Popma wrote: I also like this idea and agree with separate accounts for each component. On Fri, Dec 31, 2021 at 7:48 AM Gary Gregory wrote: Great idea. I would suggest one account for the each component. I'm not sure anyo

Re: [VOTE] Release log4net 2.0.14

icker On Dec 28, 2021, at 16:11, Davyd McColl wrote: Hi Matt, I'm happy to, just need to get the time to do the actually release (: holiday mode has kicked in good and proper. Can I close out before I release? -d On December 28, 2021 21:37:21 Matt Sicker wrote: Seems like we have enoug

Re: [VOTE] Release log4net 2.0.14

wrote: * old-log4net.snk.gpg has been the old key to sign binaries. * @Matt, where is the root logging KEYS file located? The changes in the release look good to me. +1 On Mon, 20 Dec 2021 at 07:34, Davyd McColl wrote: Thanks Matt Since you've given a +1, I'll write up some

Re: [VOTE] Release log4net 2.0.14

erl script version), contain appropriate LICENSE and NOTICE (besides the outdated copyright year, but not a blocker), no binaries in the source zip, appropriate files in the binary zip. -- Matt Sicker On Dec 16, 2021, at 07:47, Davyd McColl wrote: Hi all I'd like to raise a vote to

Re: [VOTE] Release log4net 2.0.14

lease artifacts at GitHub too. -d On 2021-12-17 08:28:35, Davyd McColl wrote: Hi Robert Binaries are signed with my key, though I remember someone raising that my key wasn't in a known area last time, so I'd appreciate help with that. I had a key signing party with Ralph and Matt quite

Re: [VOTE] Release log4net 2.0.14

log4net site? I would like to verify that the log4net website looks good in staging. Cheers Dominik On Thu, 16 Dec 2021 at 15:09, Davyd McColl wrote: Hi all I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the pre-release page at https://github.com/apache/logging-lo

Re: [VOTE] Release log4net 2.0.14

m to be valid, or I don't have the pubkey. Which key is it signed with? -Robert Middleton On Thu, Dec 16, 2021 at 8:47 AM Davyd McColl wrote: Hi all I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the pre-release page at https://github.com/apache/logging-log4

[VOTE] Release log4net 2.0.14

Hi all I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the pre-release page at  https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.14-rc1 I have updated staging docs and I _think_ I've done the right thing with respect to getting binaries and source up to the

[VOTE] Release log4net 2.0.14

Hi all I'd like to raise a vote to release log4net 2.0.14. Changelog is up on the pre-release page at https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.14-rc1 I have updated staging docs and I _think_ I've done the right thing with respect to getting binaries and source up to the de

Re: log4net

Hi Joe No, it shouldn't, particularly because we're very different projects, on very different platforms, and I understand that the log4j vuln is largely linked to a _dependency_ of log4j. The closest we've had was an xml vuln that was patched some time ago. That being said, I'm currently t

Re: [Vote] Release log4net 2.0.13-rc2

Thanks Ralph, appreciated. -d On November 7, 2021 09:54:55 Ralph Goers wrote: I have committed the release files to https://dist.apache.org/repos/dist/release/logging/log4net/ Ralph On Nov 2, 2021, at 8:56 AM, Davyd McColl wrote: Hi Ralph Yes. I'd gladly upload them myself if

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

Hi asf-staging branch merged into asf-site and I can see the latest release notes are up Apologies again for missing this. -d On 2021/11/05 16:31:41, Davyd McColl wrote: Apologies - staging docs have not been set live ): I'll have a look at it now -d On 2021/11/05 16:24:55, Volkan Y

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

Apologies - staging docs have not been set live ): I'll have a look at it now -d On 2021/11/05 16:24:55, Volkan Yazıcı wrote: I think this message is best suited for this mailing list. Would anybody from the log4net crew mind addressing the request of John Bigler, please? -- Forwarded

Re: [Vote] Release log4net 2.0.13-rc2

8:35:07, Ralph Goers wrote: How do I download the files from there? Ralph On Nov 1, 2021, at 11:12 PM, Davyd McColl wrote: Hi Thanks all for the +1's; please can someone with access copy the binaries from the GitHub release (I've renamed to https://github.com/apache/logging-log4net

Re: [Vote] Release log4net 2.0.13-rc2

: How do I download the files from there? Ralph > On Nov 1, 2021, at 11:12 PM, Davyd McColl wrote: > > Hi > > Thanks all for the +1's; please can someone with access copy the binaries > from the GitHub release (I've renamed to > https://github.com/apache/logg

Re: [Vote] Release log4net 2.0.13-rc2

Hi again 2.0.13 is up on nuget, so the only missing piece of the puzzle is the build artifacts to be up on download.apache.org, whenever someone has a gap to assist. Thanks for the vote (: -d On 2021/11/02 08:13:08, Davyd McColl wrote: Hi Thanks all for the +1's; please can someone

Re: [Vote] Release log4net 2.0.13-rc2

AL] Re: [Vote] Release log4net 2.0.13-rc2 > > +1 > > Ralph > >> On Oct 31, 2021, at 5:52 AM, Robert Middleton wrote: >> >> Looks good to me. >> >> +1 >> >> -Robert Middleton >> >> On Fri, Oct 29, 2021 at 6:08 PM Davyd McColl wrote:

Re: [Vote] Release log4net 2.0.13-rc2

Thank-you Remko -d Sent from Mailspring (https://getmailspring.com/), the best free email app for work On Oct 29 2021, at 11:04 pm, Remko Popma wrote: > +1 > > On Sat, Oct 30, 2021 at 2:13 AM Davyd McColl > wrote: > > > Hi > > > > I'd like to raise a vote

[Vote] Release log4net 2.0.13-rc2

Hi I'd like to raise a vote to release log4net 2.0.13 (this is an rc2 where the only difference is the archive layout for the associated source and binary artifacts) - there's an rc up at GitHub with release notes:  https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.13-rc2 - docume

Re: [VOTE] Release log4net 2.0.13

Thanks Matt I'm cancelling this vote in deference to the new one. -d On October 29, 2021 17:21:09 Matt Sicker wrote: Just reply to the old vote thread with a message saying you’re cancelling the vote. On Oct 29, 2021, at 9:29 AM, Davyd McColl wrote: Hi Ralph I'm not s

Re: [VOTE] Release log4net 2.0.13

the subject. I apologize for not replying earlier. Ralph > On Oct 28, 2021, at 12:48 AM, Davyd McColl wrote: > > Update: I've added a 2.0.13 RC2 release at GitHub with the suggested > modifications to release artifacts (source and binary zips). The released > functionality rem

Re: [VOTE] Release log4net 2.0.13

Update: I've added a 2.0.13 RC2 release at GitHub with the suggested modifications to release artifacts (source and binary zips). The released functionality remains unchanged. -d On 2021/10/28 08:49:23, Davyd McColl wrote: Hi Robert Thanks for checking all these things and feeding back

Re: [VOTE] Release log4net 2.0.13

h may be unexpected. Your key doesn't seem to be in the KEYS file for logging, so I can't check that: https://www.apache.org/dist/logging/KEYS -Robert Middleton On Wed, Oct 27, 2021 at 2:10 AM Davyd McColl wrote: > > Hi > > I'd like to raise a vote to release log4net

[VOTE] Release log4net 2.0.13

Hi I'd like to raise a vote to release log4net 2.0.13 - there's an rc up at GitHub with release notes:  https://github.com/apache/logging-log4net/releases/tag/rc%2F2.0.13 - documentation is updated on staging:  https://logging.staged.apache.org/log4net/ I do, however, require some assistance wit

RE: Re: Fix for Issue Log4net-611

p the new version get released. In fact, let me know if there is anything I can do for log4net in general. Always wanted to be part of an open source project in a more real way. Thanks David -----Original Message- From: Davyd McColl Sent: Sunday, October 24, 2021 4:07 PM To: dev@logging.apache.

Re: Fix for Issue Log4net-611

Hi I'll try get some time to look at this this week. There's another small fix I'd like to make and I've been putting it off because the release process is such a mission (the apache way of doing things - unlike my libraries which I can just release, log4net has to go through a vote and republ

Re: Log4Go

am not sure if that gives you the ability to create a new repo. But before doing that I would create a confluence page to lay out the initial requirements and design. If you can’t create a repo and would like one I can certainly help with that. Ralph > On Jun 30, 2021, at 12:44 PM, Davyd McC

Re: Re: Log4Go

I'm rather new to go, but looking for ways to improve by writing code alongside people who actually know what they're doing. If I can help, please ping me. -d On June 30, 2021 18:12:46 Christofer Dutz wrote: Hi all, and sorry for being late to the party ;-) I am currently working hard on

Re: [meta] What's been going on with log4net, log4cxx, and chainsaw? Request for reports

Hi Matt log4net has been quite quiet over the last quarter, partly because I took a break from all things code for a month, and partly because I'm still trying to pick up momentum after that break! However, there has been minor movement at GitHub, and your mail has reminded me to get back on t

Re: [LOG4NET] Vote for release: 2.0.12

Thanks Ralph -d On October 26, 2020 18:48:30 Ralph Goers wrote: The files were added to the distribution directory. Ralph On Oct 26, 2020, at 9:22 AM, Ralph Goers wrote: OK +1 to these. Ralph On Oct 26, 2020, at 8:57 AM, Davyd McColl wrote: Ralph, here's the 2.0.12 thread

[Announce] [log4net] release 2.0.12

Hi all I'd like to announce the release of log4net 2.0.12, which resolves issues LOG4NET-652 AND LOG4NET-653, both of which are related to correctly retrieving the username for the current thread, which would throw an exception on non-win32 platforms. The site is up, nupkg is released, pleas

Re: [LOG4NET] Vote for release: 2.0.12

Ralph, here's the 2.0.12 thread where Matt and Remko voted. -d On October 23, 2020 17:57:31 Davyd McColl wrote: Thanks Matt I think I need 3 to release... Any other takers? -d On October 23, 2020 17:33:19 Matt Sicker wrote: It seems I forgot to add my +1 here. On Mon, 19 Oct 20

Re: [VOTE] [log4net] Release 2.0.11

to do a release without a hiccup :| -d On 2020/10/26 16:35:46, Davyd McColl wrote: Hi Matt Thanks, I still forget some of the dots and crosses ): -d On 2020/10/26 16:20:58, Matt Sicker wrote: Yes, an email confirming the vote passed along with the tally. Then, after everything has been uploaded

Re: [VOTE] [log4net] Release 2.0.11

Oct 2020 at 06:58, Davyd McColl wrote: > > By results, I understand you mean a tally? There were only three votes, all > positive. I've pushed the nupkg. > > -d > > > On October 26, 2020 13:35:15 Apache wrote: > > > You need to close the vote thread with the r

Re: [VOTE] [log4net] Release 2.0.11

11:24 PM, Davyd McColl wrote: Thanks Ralph Could you assist with getting artifacts up to downloads.apache.org? I'm going to push the nupkg because people are waiting on it, and will have to set the new documentation live because people will expect it, but right now, the download links

Re: [VOTE] [log4net] Release 2.0.11

10/25 01:21:15, Ralph Goers wrote: My +1 Ralph > On Sep 22, 2020, at 11:21 PM, Davyd McColl wrote: > > Thanks all; I've completed the release as far as I can (Ralph, please push > the relevant artifacts from > https://github.com/apache/logging-log4net/releases/tag/rel%2F2.0

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

Hi Dominik iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user name on !win32, is waiting on one more +1 vote for release. -d On October 23, 2020 18:05:18 Dominik Psenner wrote: See the message below. -- Sent from my phone. -- Forwarded message - Fro

Re: [LOG4NET] Vote for release: 2.0.12

Thanks Matt I think I need 3 to release... Any other takers? -d On October 23, 2020 17:33:19 Matt Sicker wrote: It seems I forgot to add my +1 here. On Mon, 19 Oct 2020 at 01:45, Davyd McColl wrote: Hi Remko Yes, this is a vote thread -- thanks for your +1 (: Matt, I've fortun

Re: [LOG4NET] Vote for release: 2.0.12

arounds, it’s not a release blocker > at least. > >> On Sun, Oct 18, 2020 at 23:14 Davyd McColl wrote: >> >> Hi Matt >> >> Looks like the culprit is gulp-zip, specifically, the source I see sets >> mode for files but not folders (with a source comment about w

Re: [LOG4NET] Vote for release: 2.0.12

s since they're doing it wrong. :) On Sun, 18 Oct 2020 at 13:55, Davyd McColl wrote: Hi Matt Zip files are created from windows as there are certain targets that Unix compiles can't hit (specifically < net40 and client profiles), which would probably explain the permissions. Not a

Re: [LOG4NET] Vote for release: 2.0.12

Oct-18 17:22 net20/log4net.dll ... The directories need to be executable to be able to list files from them (Unix/POSIX). I'm not sure how these zip files got these permissions. I see that the previous 2.0.10 release of log4net has the same problem, though. On Sun, 18 Oct 2020 at 11:03, Davyd McCol

[LOG4NET] Vote for release: 2.0.12

Hi all Not much has changed in 2.0.12 except that an issue affecting non-windows users has been addressed. LOG4NET-652 and LOG4NET-653 both stem from the same source, wherein the username for the current logging thread was not correctly retrieved on non-windows platforms and would throw a Platf

Re: [VOTE] [log4net] Release 2.0.11

at 04:23 Dominik Psenner wrote: > +1 > > > > -- > > Sent from my phone. Typos are a kind gift to anyone who happens to find > > them. > > > > On Tue, Sep 22, 2020, 08:37 Davyd McColl wrote: > > > > > Hi all > > > > > > I&#x

Re: [VOTE] [log4net] Release 2.0.11

> Ralph > > > On Sep 20, 2020, at 1:01 PM, Matt Sicker wrote: > > > > I sent a Google Meet invite to you. > > > > On Sun, 20 Sep 2020 at 14:26, Davyd McColl wrote: > >> > >> I'm happy to be available at 8am my side, if that works for

Re: [VOTE] [log4net] Release 2.0.11

s wrote: 8am in Durban South Africa is 11pm the night before in Phoenix AZ. However, I frequently am up until midnight so that could work. 5-5:30 pm is 7:30-8 am in Phoenix. I usually am not in front of my computer on a weekday until 8 am but on occasion I can do earlier. Ralph On Sep 20,

Re: [VOTE] [log4net] Release 2.0.11

idea could work for exchanging keys. What times would you be available to do that? On Sun, Sep 20, 2020 at 03:09 Davyd McColl wrote: Hi Ralph I think I miscommunicated: I'm not regenerating my signing key - just the nuget API key for package upload. This forces me to log in in nuget.org

Re: [VOTE] [log4net] Release 2.0.11

o you are building a web of trust. Sooner or later there will be someone in that web that you personally know and trust. Ralph On Sep 19, 2020, at 11:26 PM, Davyd McColl wrote: Thanks Matt, I've updated the artifacts on GitHub to have detached signatures. I had previously also uploaded

Re: [VOTE] [log4net] Release 2.0.11

ing/log4net/KEYS [2]: https://downloads.apache.org/logging/KEYS [3]: https://infra.apache.org/release-signing.html#keys-policy On Sat, 19 Sep 2020 at 12:48, Davyd McColl wrote: > > Thanks Matt, I've done so. Hopefully that makes it easier to verify > artifacts that I have signed. > >

Re: [VOTE] [log4net] Release 2.0.11

Sep 2020 at 15:53, Matt Sicker wrote: > > > > Oh sorry, I didn't notice that you uploaded them there (wasn't even > > aware that it was possible to be honest). > > > > On Fri, 18 Sep 2020 at 14:43, Davyd McColl wrote: > > > > > > Hi Matt &

Re: [VOTE] [log4net] Release 2.0.11

key? I don't think we've imported that to the KEYS > file as far as I can tell? > > On Fri, 18 Sep 2020 at 15:53, Matt Sicker wrote: > > > > Oh sorry, I didn't notice that you uploaded them there (wasn't even > > aware that it was possible to be h

Re: [VOTE] [log4net] Release 2.0.11

ave the artifacts yet since they're not released yet. :) On Fri, 18 Sep 2020 at 09:05, Davyd McColl wrote: Hi all I have another potential release available: 2.0.11, tagged as rc/2.0.11 Changes are really minor: - fixed assembly versioning (all assemblies should report 2.0.11.0 as t

[VOTE] [log4net] Release 2.0.11

Hi all I have another potential release available: 2.0.11, tagged as rc/2.0.11 Changes are really minor: - fixed assembly versioning (all assemblies should report 2.0.11.0 as their version now) - properly dispose of StreamWriters within logging appenders (thanks to @NicholasNoise) Binaries are

[VOTE] [log4net] Release 2.0.11

Hi all I have another potential release available: 2.0.11, tagged as rc/2.0.11 Changes are really minor: - fixed assembly versioning (all assemblies should report 2.0.11.0 as their version now) - properly dispose of StreamWriters within logging appenders (thanks to @NicholasNoise) Binaries are

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

x for an invalid version string for one of the client profile version strings and a good few places where StreamWriters weren't being disposed, so it's not for nought) Thanks again for notifying me. -d On 2020/09/18 13:10:26, Davyd McColl wrote: hm, that's not great ): I'll

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

hm, that's not great ): I'll investigate. Thanks for letting me know! -d On 2020/09/18 13:05:58, Dominik Psenner wrote: See the message below. Apparently something went wrong during the last release. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. -- For

Re: [VOTE] [log4net] Release 2.0.10

n Sep 12, 2020, at 9:02 AM, Davyd McColl wrote: 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 s

Re: [VOTE] [log4net] Release 2.0.10

t; >> +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

[log4net] cleaning up JIRA

Hi all I'd like to start (at some point) clearing up JIRA a bit and getting on top of associated pull requests (for example, the one for a REST appender,  https://issues.apache.org/jira/projects/LOG4NET/issues/LOG4NET-644) and I'd appreciate any guidance on the accepted methods. To clarify, if i

Re: [VOTE] [log4net] Release log4net 2.0.10

ok. Best regards -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Thu, Sep 10, 2020, 08:48 Davyd McColl wrote: > Hi > > Sorry to be a bother, but I haven't heard anything back on this apart from > Dominik's inquiry into netstandard 1.3 su

Re: [VOTE] [log4net] Release log4net 2.0.10

nks -d On 2020/09/06 20:51:38, Davyd McColl 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 t

Re: [VOTE] [log4net] Release 2.0.10

s significantly for netstandard 2.0 users Thanks -d On 2020/09/07 21:15:42, Davyd McColl wrote: 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 (particu

Re: issues with log4net 2.0.9 under IIS for projects using .net framework 4.5+

2020, 9:59 PM Davyd McColl wrote: Thanks! I'm surprised that you had the experience you had, because those environments are very similar to ours at work. May I ask what process you use to deploy? We use Octopus. At least if I see the same odd behaviour, I have one more idea to check (:

RE: issues with log4net 2.0.9 under IIS for projects using .net framework 4.5+

ST - Enterprise Applications 2195 Hearst Avenue, 250-29 Berkeley, CA 94720-4876 510-508-4443 jmit...@berkeley.edu From: Davyd McColl Sent: Tuesday, September 8, 2020 1:18 PM To: Joseph A. MITOLA Cc: dev@logging.apache.org Subject: RE: issues with log4net 2.0.9 under IIS for projects using .net

RE: issues with log4net 2.0.9 under IIS for projects using .net framework 4.5+

rences. Thanks for all your help, Joseph Joseph A. Mitola, Information Systems Analyst University of California, Berkeley IST - Enterprise Applications 2195 Hearst Avenue, 250-29 Berkeley, CA 94720-4876 510-508-4443 jmit...@berkeley.edu From: Davyd McColl Sent: Tuesday, September 8, 2020 1

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

er 8, 2020 19:08:55 Matt Sicker wrote: That's this dev list! Though if we need a separate mailing list, we can always create more. On Tue, 8 Sep 2020 at 11:54, Davyd McColl wrote: What if there was another Apache email address that messages were sent to, and multiple people could observe

RE: issues with log4net 2.0.9 under IIS for projects using .net framework 4.5+

ssing because assemblies further up the chain are expecting a different version or an assembly with a different public key. -d On 2020/09/08 18:52:09, Davyd McColl wrote: Have you tried an assembly rebind to force resolution to 2.0.9? -d On September 8, 2020 18:00:45 "Joseph A. MITOLA

RE: issues with log4net 2.0.9 under IIS for projects using .net framework 4.5+

ons 2195 Hearst Avenue, 250-29 Berkeley, CA 94720-4876 510-508-4443 jmit...@berkeley.edu From: Davyd McColl Sent: Tuesday, September 8, 2020 12:08 AM To: jmit...@berkeley.edu Cc: dev@logging.apache.org Subject: RE: issues with log4net 2.0.9 under IIS for projects using .net framework 4.5+ Hi Jose

  1   2   >