Hi all
I'm new to this list, been using log4net for around 9 years, and only this
week discovered that it is being made dormant (and what that means).
I've been told that the team has been looking for outside help for around 2
years, with no-one forthcoming. Unfortunately, as I say, this is the f
come forward and are working towards a release. We hope
they succeed.
Ralph
On Apr 5, 2020, at 11:56 PM, Davyd McColl wrote:
Hi all
I'm new to this list, been using log4net for around 9 years, and only
this
week discovered that it is being made dormant (and what that means).
I've b
ished.
There is a big difference between us reviewing PRs and merging them for
stuff we know little about vs us providing the karma you will need to
formally get a release done.
Ralph
On Apr 6, 2020, at 12:57 PM, Davyd McColl wrote:
Unfortunately, this would suggest that forking and publishin
how to perform a
release. We know there have been fixes committed that are needed. We just don’t
know how to make them available. That is exactly why I said your focus should
be getting a release built.
Ralph
> On Apr 6, 2020, at 10:15 PM, Davyd McColl wrote:
>
> That sounds promisin
y invite anyone who does such a
release to join the PMC so that they'd have the proper authorization
to perform all the release steps on their own (other than the vote
itself which we would all take part in).
On Tue, 7 Apr 2020 at 09:18, Davyd McColl wrote:
>
> I'm glad to help --
that's also supported.
On Tue, 7 Apr 2020 at 10:46, Ralph Goers wrote:
>
> You should feel free to change the build system in any way that makes it
> easier for people to perform a release. Ideally, it would be nice if it was
> something that could be automated from Jenkin
, or one of the
others who has expressed an interest in Log4Net, could respond to them.
Ralph
> On Apr 7, 2020, at 11:18 PM, Davyd McColl wrote:
>
> Thanks Matt
>
> To clarify my plans, I will:
> 1. update the build system for log4net: I haven't seen any objection to using
&g
https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-inline-tasks?view=vs-2019
On Wed, 8 Apr 2020 at 08:56, Davyd McColl wrote:
On progress reports: sure, I'll try to keep this list updated
On PRs: I'm happy to start helping once I've spent more time in the
codebase (whi
Hi all
Since there was interest in intermittent status updates, here's a short one:
1. Packaged & released my build scripts as an npm module (zarro)
2. Consolidated the netstandard and main log4net projects and re-organised the
code locations to be more consistent with .net style: src folder cont
A short update (not much to report):
- resolved Client profile builds
- can manually build a .nupkg, without any warnings
- have updated to , using the term Apache-2.0, as per
the url it was pointing to
- have updated to point at the same feather.png the package used to
point to online, re
om/apache/logging-log4net/tree/feature/netstandard-2.0/buildtools/docker>
There are dockerfiles along with shell scripts that used to work for
building several of the targets.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Sat, Apr 18, 2020, 17:02 Davyd McC
Hi
Quick question: what operating system does the available CI server run?
Even if docker is an option, the host system is matters.
Thanks
-d
Thanks for the reply (:
Would external build systems like circleci be acceptable too?
-d
On April 25, 2020 21:03:01 Matt Sicker wrote:
Info about our existing infra is documented here:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins
On Sat, 25 Apr 2020 at 13:38, Davyd McColl
avisCI to build with
varying approaches.
-d
On 2020-04-25 22:15:36, Matt Sicker wrote:
The only external build systems that are set up for Apache right now
are Travis and some limited GitHub Action experiments. Other CI
systems may need to talk with Apache Infra.
On Sat, 25 Apr 2020 at 14:47
apache.org/services.html
>
> If nothing on there is appropriate, I think we need to create a Jira
> ticket in https://issues.apache.org/jira/browse/INFRA
>
> On Mon, 27 Apr 2020 at 01:28, Davyd McColl wrote:
> >
> > What would need to be done to make other CI systems talk wi
tches may not be mergable
into develop/master either as they could live in their own branch if
necessary.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Mon, Apr 27, 2020, 21:13 Davyd McColl wrote:
Thanks, I've already tried using mono for cross-compi
have no idea if that
limitation in CircleCI has ever been fixed.
On Mon, 27 Apr 2020 at 14:55, Davyd McColl wrote:
>
> If supporting them can come at minimal or zero cost, I don't see why not.
> As stated before, this is already achieved within CircleCI, so I guess now
> it's
Hi all
I've been a bit busy with other stuff lately, but played a little catch-up
today:
- I have a _windows_ docker image (and batch file) which builds log4net fine
- I've sorted out AppVeyer -- builds happen fine there too. I get the nuget
package as a build artifact -- I'd guess that, at som
windows/.
Have you documented the instructions to perform the build somewhere?
Ralph
> On May 3, 2020, at 9:23 AM, Davyd McColl wrote:
>
> Hi all
>
> I've been a bit busy with other stuff lately, but played a little catch-up
> today:
>
> - I have a _windows_ docke
dware if that
helps. I perform all the Log4j releases on my MacBook Pro.
That said, I am sure it would be helpful to have Docker available to preform CI
builds.
Ralph
> On May 3, 2020, at 10:23 AM, Davyd McColl wrote:
>
> Hi Ralph
>
> I'll add documentation about build, tho
Please let me know if I can help with that - if you're using the new build
process I made and something doesn't work as expected, I'm happy to help.
On July 18, 2020 02:58:03 Matt Sicker wrote:
I've finished migrating all our jobs that I could find. There's a
log4net pipeline that I could po
Hi all, I've never done this before, so bear with me if I fluff it:
This is a proposed vote to release log4net 2.0.9 from PR
https://github.com/apache/logging-log4net/pull/61
Release artifacts (including source zip) are at:
https://ci.appveyor.com/project/fluffynuts/logging-log4net/builds/34063
Apologies if there's any confusion around sender address -- I've already
fluffed this by sending from my work account (default in my mail client)
-d
On 2020/07/31 08:26:54, Davyd McColl wrote:
Hi all, I've never done this before, so bear with me if I fluff it:
This is a p
istributable files. As a bonus, you can also sign the git tag you
created with the same key, but that's not required.
On Fri, 31 Jul 2020 at 01:28, Davyd McColl wrote:
Apologies if there's any confusion around sender address -- I've already
fluffed this by sending from my work acco
n Tue, Aug 4, 2020 at 12:25 PM Matt Sicker wrote:
Hi,
It is my pleasure to announce to the community that Davyd McColl has
joined our ranks.
He made remarkable contributions to log4net working towards
resurrecting the log4net community and making a new release, and we
all believe he is a val
1 Remko.
> > >
> > > On Tue, Aug 4, 2020 at 1:04 AM Matt Sicker wrote:
> > >
> > >> +1 from me. We can handle the release signing afterwards as Ralph
suggests.
> > >>
> > >> On Mon, 3 Aug 2020 at 10:30, Ralph Goers
> > >&g
te to reflect
> that it is no longer dormant.
>
> Ralph
>
> > On Aug 16, 2020, at 11:54 AM, Matt Sicker wrote:
> >
> > Thanks so much for your help in releasing this!
> >
> > On Sun, 16 Aug 2020 at 13:53, Davyd McColl wrote:
> >>
> >> I&
the download links on the
logging.apache.org site.
As for nuget, I'm not sure about that.
On Mon, 17 Aug 2020 at 01:56, Davyd McColl wrote:
Great!
How do we get the nupkg to nuget.org? This is the final step that most
users are going to be interested in.
Having a look at what's at
be in the set of recipients with their
gpg key.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Mon, Aug 17, 2020, 08:56 Davyd McColl wrote:
Great!
How do we get the nupkg to nuget.org? This is the final step that most
users are going to be interested in.
ssful vote? With this, anyone having the
possibility to push a tag can forge a release with almost no effort.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Mon, Aug 17, 2020, 19:21 Davyd McColl wrote:
Correct, nuget publish. An option, once I'm trus
ik Psenner
wrote:
>>>>>
>>>>> I guess that would be a nuget publish.
>>>>>
>>>>> https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package
>>>>>
>>>>> The credentials to that account are stored
g/keys/group/logging-pmc.asc <
>> https://people.apache.org/keys/group/logging-pmc.asc>. That url
returns
>> a 404. Any idea where it moved to?
>> >>>>
>> >>>> Ralph
>> >>>>
>> >>>>> On Aug 17, 2020, at 9:39
limited:
https://docs.microsoft.com/en-us/nuget/nuget-org/organizations-on-nuget-org#managing-organization-members
Cheers
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Sat, Aug 22, 2020, 21:54 Davyd McColl wrote:
Oh ok, well, mine is davydm (:
-d
On August
at the release vote was for.
>
> Ralph
>
> > On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote:
> >
> > Thanks Dominik
> >
> > Are there any objections to me pushing the 2.0.9 package that had been
> > approved and uploaded to https://downloads.apache
That's a good catch; the url should be updated (I'll put that on my TODO) and
I'd raise that perhaps logging.apache.org should auto-redirect to https?
-d
On 2020/08/24 14:16:04, Dominik Psenner wrote:
Hi,
I noticed that the site url of the log4net nuget package is http instead of
https (http:/
Ralph, I'm happy to -- but I have no idea how to. Even a pointer at a document
I can read on how would be greatly appreciated (ie how to get content to the
website)
-d
On 2020/08/26 16:54:46, Ralph Goers wrote:
Davyd, Can you update the web site? It still says Log4Net is dormant and does
not
Hi
Matt, I don't think that CVE is fixed in 2.0.9. I originally tracked down a
commit in the develop branch which had the change in it, and I'm quite sure
that commit was never brought into the 2.0.9 release. The changes I made on
that branch were all around build, simply to try to get the proj
Thanks Matt, I'll give that a go tonight (:
-d
On 2020/08/26 17:07:00, Matt Sicker wrote:
I think these instructions are still up to date:
https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Site
On Wed, 26 Aug 2020 at 10:02, Davyd McColl wrote:
>
, at 8:06 AM, Matt Sicker wrote:
I think these instructions are still up to date:
https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Site
On Wed, 26 Aug 2020 at 10:02, Davyd McColl wrote:
Ralph, I'm happy to -- but I have no idea how to. Even a pointer
ind via a quick text-search).
I'll report back when I have something that works.
-d
On 2020/08/26 17:26:18, Davyd McColl wrote:
Thanks Ralph, will give that all a go tonight!
-d
On August 26, 2020 17:24:40 Ralph Goers wrote:
Building the site should just require running
mvn site
in the h
n the generated output (eg releases)
are broken (target html is missing). For all I know, the targets _should_ be
missing? ie, they're maintained by hand? I dunno.
-d
On 2020/08/26 18:18:15, Davyd McColl wrote:
update: I have the site building with maven, but a _lot_ of the links are
broken
hen I have some
time.
Ralph
> On Aug 26, 2020, at 10:22 AM, Davyd McColl wrote:
>
> I've raised a PR in the interim: all I've done is move the site assets back
> where they belong (I inadvertently moved them out when refactoring for
> build!). I have a lot to learn to un
G4NET-563, which doesn't really affect the package release, looks
like the commit was to update the site styling to be in line with log4j
I only made the first listed change myself -- the others were largely due to
the efforts of Stephan Bodewig and Dominik Psenner.
-d
On 2020/08/26 19:43:46
Hi all
I've been trying to update content for http://logging.apache.org/log4net (in
particular http://logging.apache.org/log4net/release) and I'm sure I'm just
doing something silly or missing something.
I've followed instructions at
https://cwiki.apache.org/confluence/display/LOGGING/Managing
Thanks
-d
On 2020/08/28 16:07:45, Apache wrote:
I will take care of the main logging site. It currently uses the ASF CMS but we
have to get off of it so there isn’t much point in you having to learn how to
deal with it.
Ralph
> On Aug 28, 2020, at 12:26 AM, Davyd McColl wrote:
>
>
Ralph, the log4net download link points to a cgi script; I've updated the
associated download_log4net.html as I think would be correct, but I'll only
know once it's run through the cgi script (which simply refers to an external
script, so doesn't really tell me what it does or expects). I gather
handles mirror redirects or CDN
or whatever it’s implemented as right now. That CGI script is ancient and
is no longer necessary as of, oh, many years I think? 😉
On Tue, Sep 1, 2020 at 01:17 Davyd McColl wrote:
> Ralph, the log4net download link points to a cgi script; I've updated the
&g
yone!
>>
>> On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote:
>>
>>> Thanks again for managing the release! I’m sure you’ve just made a lot of
>>> developers happy. :D
>>>
>>> On Mon, Aug 24, 2020 at 01:40 Davyd McColl wrote:
>>>
>>
hed. You should have permission to publish the web
site already.
I will try to verify your changes tomorrow.
Ralph
> On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote:
>
> Hi Ralph
>
> The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously
> forgot to push
release distribution for quite some time (svn
seems better suited for archiving binary files like that).
On Wed, 2 Sep 2020 at 04:17, Davyd McColl wrote:
>
> I'm not following ):
>
> Previously, when I updated SVN, you said that it wasn't the way to do it.
>
> Is there a
rect. The heading still says 2.0.8 although the source
zip is 2.0.9 as it should be. The binary artifacts display as 2.0.8 but the
links point to 2.0.9. Log4j controls all of this with a variable in the pom.xml
file.
Ralph
> On Sep 2, 2020, at 11:01 PM, Davyd McColl wrote:
>
> R
Thanks
-d
On September 5, 2020 21:16:23 Ralph Goers wrote:
The changes looked good to me so I went ahead and merged them to the
asf-site branch so now they are on the live site.
Ralph
On Sep 4, 2020, at 11:51 PM, Davyd McColl wrote:
Hi Ralph
Sorry for wasting your time. I stupidly
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
supply chain from the release manager
(you in this case) to the end user.
[you = Davyd]
On Sun, 6 Sep 2020 at 13:33, Davyd McColl wrote:
>
> Thanks Matt
>
> I was trying to use GitHub's release feature to create a draft release to
> present binaries including signing and has
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
nd 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.10 of log4net, with:
- updated netstandard 2
Hi Ralph
I'll investigate this today. I'd like more information, particularly
configuration and, eg if the ado.net appender is used, table structures.
Joseph, please open a ticket at
https://issues.apache.org/jira/browse/LOG4NET to help me track this.
-d
On September 7, 2020 23:35:12 Ral
end
of the day, I'd like the situation to be better for both the PMC and users. I'm
open to any suggestions.
-d
On 2020/09/08 07:24:25, Davyd McColl wrote:
Hi Ralph
I'll investigate this today. I'd like more information, particularly
configuration and, eg if the ado.ne
Hi Joseph
I've performed a (rather belated) upgrade to log4net 2.0.9 on a work project
targeting net462 and, apart from having to perform some assembly rebinds to
handle dependencies which expect log4net 2.0.8, it's working fine with an
ado.net appender and a rolling log file appender, so I'd r
r the official project website.
--
Sent from my phone. Typos are a kind gift to anyone who happens to find
them.
On Tue, Sep 8, 2020, 08:34 Davyd McColl wrote:
> Ralph
>
> I understand that the emails provide a bit of workload, and I'm trying to
> figure out a solution to help
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
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
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
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
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
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 (:
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
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
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
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
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
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
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
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
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
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
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
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
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
&
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.
>
>
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
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
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,
> 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
1 - 100 of 163 matches
Mail list logo
