Hi all
With +3 binding votes (Christian, Volkan and myself), apache log4net
2.0.17 is released and available:
https://github.com/apache/logging-log4net/releases/tag/rel%2F2.0.17
Source snapshot at:
https://downloads.apache.org/logging/log4net/source/apache-log4net-source-2.0.17.zip
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
+1
Checked sigs, hashes, `LICENSE` files, and release notes.
On Fri, Mar 15, 2024 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
omes from package.json and will only show when running npm commands. But I
> >> admit it's confusing.
> >>
> >> -d
> >>
> >> On 15 March 2024 16:28:47 "Gary D. Gregory" wrote:
> >>
> >>> We might need better build instructions..
and will only show when running npm commands. But I
>> admit it's confusing.
>>
>> -d
>>
>> On 15 March 2024 16:28:47 "Gary D. Gregory" wrote:
>>
>>> We might need better build instructions... for me at least ;-)
>>>
>>> I take i
should be removed since it's not mentioned
>> in https://github.com/apache/logging-log4net/blob/master/doc/BUILDING.md
>> ?
>>
>> BUILDING.md contains a section called "TL;DR (!Windows):" which is too
>> easy to confuse with "TL;DR (Windows):", j
:28:47 "Gary D. Gregory" wrote:
We might need better build instructions... for me at least ;-)
I take it the build.cmd file should be removed since it's not mentioned in
https://github.com/apache/logging-log4net/blob/master/doc/BUILDING.md ?
BUILDING.md contains a section cal
We might need better build instructions... for me at least ;-)
I take it the build.cmd file should be removed since it's not mentioned in
https://github.com/apache/logging-log4net/blob/master/doc/BUILDING.md ?
BUILDING.md contains a section called "TL;DR (!Windows):" which i
yourself.
On Fri, Mar 15, 2024 at 3:05 PM Gary D. Gregory wrote:
>
> Hi and thank you for RM'ing this release.
>
> > https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1
>
> This is no good IMO, you should provide an _apache_ link.
>
> Gary
>
> On
Hi and thank you for RM'ing this release.
> https://github.com/apache/logging-log4net/releases/tag/rel/2.0.17-rc1
This is no good IMO, you should provide an _apache_ link.
Gary
On 2024/03/15 12:28:03 Davyd McColl wrote:
> Hi all,
>
> This is a vote to release the Apache Lo
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
t is helpful to note
which
> votes are binding or not.
>
> Gary
>
> On Fri, Mar 8, 2024, 6:06 AM Davyd McColl wrote:
>
>> Hi all
>>
>>
>> Thanks for all the checking - log4net 2.0.16 is out in the wild now (:
>>
>>
>> -d
>>
&
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:
>
Hi Davyd,
On Fri, 8 Mar 2024 at 14:59, Davyd McColl wrote:
>
> 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 should be resolved. There were no -1's, and at
> least 4 +1's that I
for all the checking - log4net 2.0.16 is out in the wild now (:
-d
On 2024/03/08 00:02, Jan Friedrich wrote:
Hello Gary,
the errors are in the examples project for .net compact framework (which
is no longer supported by microsoft):
C:\Users\ggregory\rc\apache-log4net-source-2.0.16\examples
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:
> Hi all
>
>
> Thanks for all the checki
Hi all
Thanks for all the checking - log4net 2.0.16 is out in the wild now (:
-d
On 2024/03/08 00:02, Jan Friedrich wrote:
Hello Gary,
the errors are in the examples project for .net compact framework (which is no
longer supported by microsoft):
C:\Users\ggregory\rc\apache-log4net-source
ady on top of
Microsoft Windows [Version 10.0.19045.4046]
My results: https://paste.apache.org/jj3c8
I rebooted and tried again with the same results.
Gary
On 2024/03/07 03:11:22 Robert Middleton wrote:
+1
Verified the following:
* apache-log4net-source-2.0.16.zip and associated sha/signature
* apac
Hello Gary,
the errors are in the examples project for .net compact framework (which is no
longer supported by microsoft):
C:\Users\ggregory\rc\apache-log4net-source-2.0.16\examples\netcf\1.0\Tutorials\ConsoleApp\cs\src\ConsoleApp.csdproj(23,1):
error MSB4075:
The project file
"C:\
with the same results.
Gary
On 2024/03/07 03:11:22 Robert Middleton wrote:
> +1
>
> Verified the following:
> * apache-log4net-source-2.0.16.zip and associated sha/signature
> * apache-log4net-binaries-2.0.16.zip and associated sha/signature
>
> It looks all good to me.
&
+1
Verified the following:
* apache-log4net-source-2.0.16.zip and associated sha/signature
* apache-log4net-binaries-2.0.16.zip and associated sha/signature
It looks all good to me.
-Robert Middleton
On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers wrote:
>
> +1
>
> Verified signature
2022 as the 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
>
. (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-
+1
Verified signatures.
Verified hashes.
`NOTICE` contains 2022 as the 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
&
:
Hi,
I think I got it uploaded (from my machine).
choco install svn
svn co https://dist.apache.org/repos/dist/dev/logging -N
apache-dist-logging-dev
cd apache-dist-logging-dev
svn up log4net
svn delete .\log4net\binaries\*2.0.14.*
svn add .\log4net\binaries\*
svn add .\log4net\source\*
svn commit
Hi,
I think I got it uploaded (from my machine).
choco install svn
svn co https://dist.apache.org/repos/dist/dev/logging -N apache-dist-logging-dev
cd apache-dist-logging-dev
svn up log4net
svn delete .\log4net\binaries\*2.0.14.*
svn add .\log4net\binaries\*
svn add .\log4net\source\*
svn commit
Hi Volkan
Thanks for taking the time to explain (:
This is pretty-much what I did, as per step 16 of
https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md -
unless there's a typo I've made somewhere or something like that. That's
why I'm confused as to why I can't see
Davyd, assuming you have `svn` in the command line, following should get
the job done:
# Checkout the `dev` distribution repository
svn co https://dist.apache.org/repos/dist/dev/logging logging-dist-dev
cd logging-dist-dev
# Delete old distribution files
svn rm log4net
# Add the new
://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.apache.org/log4net/release
they are
irrelevant from an ASF point of view.
Could you upload the source distribution 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 vot
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
cedure steps over chat could save both of
you from long waiting times.
I am looking forward to the outcome! 爛
On Thu, Feb 29, 2024 at 8:56 PM Jan Friedrich wrote:
> Hi,
>
> thanks for the opportunity, I will try my best.
>
> https://github.com/apache/logging-log4net/pull/115
Hi,
thanks for the opportunity, I will try my best.
https://github.com/apache/logging-log4net/pull/115
Regards.
Jan
Thursday, February 29, 2024, 12:26:55 PM, you wrote:
> Hi Volkan
> If Jan feels up to the task, it would be worthwhile to give it a go. If
> nothing else, i
Hi,
as far as i know, setting true in csproj should
be enough for this.
See line 73 in
https://github.com/apache/logging-log4net/pull/115/files#diff-0f81264aa7e82fb31702de904a86565584da1349835af0d3b08b69d09502a384
Regards.
Jan
Thursday, February 29, 2024, 1:12:24 PM, you wrote:
> Hi Pi
Hi Piotr
I actually don't know with 100% accuracy, but I did find this:
https://www.mitchelsellers.com/blog/article/net-5-deterministic-builds-source-linking
which is a little old but might be worthwhile investigating.
-d
On 29 February 2024 13:54:47 "Piotr P. Karwasz"
wrote:
Hi
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 just a
on Friday afternoon, so I'll check it out then. In the
mean-time, if you'd like to see
how far you can get with the RELEASING.md instructions, I'd _really_
appreciate it. I haven't done
a log4net release in ages because it takes a reasonable amount of time
and motivation - substances
I'm in sh
Davyd, can Jan help you with the release? Since he is not a PMC member,
there are certain steps he can't take. Though judging from the RELEASING.md
<https://github.com/apache/logging-log4net/blob/master/doc/RELEASING.md>,
maybe he can bring it to a point within the limits of access rights g
ailing list.
> I
> VY>> will share the result next week around this time.
>
> VY>> Fred, some questions:
>
> VY>>1. Are you subscribed to `dev@` and `log4j-user@` mailing lists
> VY>><https://logging.apache.org/support.html>? If not, could you
>
t;https://logging.apache.org/support.html>? If not, could you please do
VY>>so? (Mailing lists are the official communication channels of ASF.)
VY>>2. Are you watching "All Activity" on logging-log4net
VY>><https://github.com/apache/logging-log4net>
g "All Activity" on logging-log4net
VY><https://github.com/apache/logging-log4net>? If not, could you please do
VY>so?
VY>3. Do you want to be referred to as Fred or Jan?
VY> On Thu, Feb 1, 2024 at 1:13 PM Fred am Nil wrote:
>> Hi Volkan,
>
so? (Mailing lists are the official communication channels of ASF.)
2. Are you watching "All Activity" on logging-log4net
<https://github.com/apache/logging-log4net>? If not, could you please do
so?
3. Do you want to be referred to as Fred or Jan?
On Thu, Feb 1, 2024
Fred am Nil
>
> VY> wrote:
>
> >> Hi,
> >>
> >> as proposed by Volkan Yazıcı in
> >>
> https://github.com/apache/logging-log4net/pull/103#issuecomment-1918677272
> >> I would like to become a maintainer of log4net.
> >>
> >> https://github.com/FreeAndNil
> >>
> >> Regards.
> >>
> >> Fred
> >>
> >>
>
VY> On Wed, Jan 31, 2024 at 12:01 PM Fred am Nil
VY> wrote:
>> Hi,
>>
>> as proposed by Volkan Yazıcı in
>> https://github.com/apache/logging-log4net/pull/103#issuecomment-1918677272
>> I would like to become a maintainer of log4net.
>>
>> https://github.com/FreeAndNil
>>
>> Regards.
>>
>> Fred
>>
>>
://github.com/apache/logging-log4net/pull/103#issuecomment-1918677272
> I would like to become a maintainer of log4net.
>
> https://github.com/FreeAndNil
>
> Regards.
>
> Fred
>
>
/apache/logging-log4net/pull/103#issuecomment-1918677272
I would like to become a maintainer of log4net.
https://github.com/FreeAndNil
Regards.
Fred
Hi,
as proposed by Volkan Yazıcı in
https://github.com/apache/logging-log4net/pull/103#issuecomment-1918677272
I would like to become a maintainer of log4net.
https://github.com/FreeAndNil
Regards.
Fred
?
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 ):
-d
On 2023/1
ough active PMC members, or a significant number of
>> contributors left the project, etc.
>> - *Considering moving to the Attic:* a project that's about to move to
>> the Attic, or discussing that
>>
>> IMO, Log4net can be classified as "at risk", right?
>>
tributors left the project, etc.
>- *Considering moving to the Attic:* a project that's about to move to
>the Attic, or discussing that
>
> IMO, Log4net can be classified as "at risk", right?
>
that's about to move to
the Attic, or discussing that
IMO, Log4net can be classified as "at risk", right?
t; You could base your work on that or proceed otherwise.
The path to proceed with implementation based on RFA-NG is the path to address
all the bugs, right? That is too much of a hurdle.
I considered not touching the existing bug and addressing only LOG4NET-27, but
the following comment on 2017
ion.
>
> Hello.
> Let me ask you a question.
>
> 1) Which is the best way to proceed on the topic of MaxDateRollBackups in
> RollingFileAppender?
> ・post https://issues.apache.org/jira/browse/LOG4NET-27
> ・post https://issues.apache.org/jira/browse/LOG4NET-367
>
I do not speak English, so please excuse the machine translation.
Hello.
Let me ask you a question.
1) Which is the best way to proceed on the topic of MaxDateRollBackups in
RollingFileAppender?
・post https://issues.apache.org/jira/browse/LOG4NET-27
・post https://issues.apache.org/jira
Thanks for the quick response.
I am relieved.
DeepL is awesome!
夏月 梨幸(Natsuki Rikou)
DateRollBackups in
> RollingFileAppender, but have concerns due to my lack of English speaking
> ability.
> Is it permissible to list native language and English (machine translated)
> side-by-side for C# comments and documentation comments?
>
> > https://logging.apache.org/log4net
translated)
side-by-side for C# comments and documentation comments?
> https://logging.apache.org/log4net/release/faq.html
In the URL above, I did not see any restrictions on the language used in the
comments.
> apache-log4net-source-2.0.15.zip
However, as far as the source is concerned, all co
Kevin,
I don't work on Log4net, but looking through the recent commits it
looks like this may have been fixed:
https://github.com/apache/logging-log4net/pull/92
I don't know if there is currently a timeline as to when this might be
officially released.
-Robert Middleton
On Thu, Dec 29, 2022
on your specific issue as I don’t work on Log4Net so I will
leave that to those that do.
Ralph
> On Dec 29, 2022, at 1:24 PM, Seal, Rupak
> wrote:
>
> HI @Tools Support<mailto:toolssupp...@schwab.com> is there any ways to have
> this work being escalated as this impacted
o: dev@logging.apache.org
Cc: Joshi, Hemant , Vishwakarma, Amit
, Seal, Rupak ,
Shambhumane, Meenakshi
Subject: Log4Net 2.014
Hi,
We recently upgraded our Log4Net package from 1.2.13 to 2.0.14 to remediate a
security flaw found in the old package. After upgrading we have found an issue
that is not allo
Hi,
We recently upgraded our Log4Net package from 1.2.13 to 2.0.14 to remediate a
security flaw found in the old package. After upgrading we have found an issue
that is not allowing 2 instances of an application to write to the same file
location. We have a blue/green pool deployment strategy
Hello,
In our CI pipeline, we detected vulnerability CVE-2021-24112, which affects
the System.Drawing.Common 5.0.0 package, which is a dependency of log4net
2.0.15.
> dotnet list package --vulnerable --include-transitive
> System.Drawing.Common 5.0.0 Critical
26, 2022, at 6:25 PM, Robert Middleton
> > > > > wrote:
> > > > > The binaries won't show up under downloads.apache.org
> > > > > (http://downloads.apache.org) until actually
> > > > > released(e.g. under repos/dist/release/logging/log4
downloads.apache.org until actually
released(e.g. under repos/dist/release/logging/log4net). That can of
course only happen after the release 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
ert Middleton wrote:
>>>
>>> The binaries won't show up under downloads.apache.org until actually
>>> released(e.g. under repos/dist/release/logging/log4net). That can of
>>> course only happen after the release is done via this vote.
>>>
>>
+1
I validated the signatures and hashes. I also don’t have a .NET environment so
didn’t build or test.
Ralph
> On Jul 25, 2022, at 12:52 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 log
t dist/release/log4net and the artifacts are there. This
> means you have already released the artifacts publicly despite the vote
> having not completed. You cannot really remove them as they propagate to
> mirrors fairly quickly.
>
> You need to create a confluence page with the relea
But I just looked at dist/release/log4net and the artifacts are there. This
means you have already released the artifacts publicly despite the vote having
not completed. You cannot really remove them as they propagate to mirrors
fairly quickly.
You need to create a confluence page
But never mind. Now that I look I see that dist/dev/log4net has a binaries and
sources directory. I am used to the way log4j does it where they are together.
So they are there.
Ralph
> On Jul 29, 2022, at 3:20 PM, Ralph Goers wrote:
>
> You publish to dist/dev for the vote.
t;>>
>>>> On Jul 26, 2022, at 6:25 PM, Robert Middleton
>>>> wrote:
>>>>
>>>> The binaries won't show up under downloads.apache.org until actually
>>>> released(e.g. under repos/dist/release/logging/log4net). That can of
>>>> cou
> On Jul 26, 2022, at 6:25 PM, Robert Middleton
> >> wrote:
> >>
> >> The binaries won't show up under downloads.apache.org until actually
> >> released(e.g. under repos/dist/release/logging/log4net). That can of
> >> course only happen after the release is done via t
dleton
> >> wrote:
> >>
> >> The binaries won't show up under downloads.apache.org until actually
> >> released(e.g. under repos/dist/release/logging/log4net). That can of
> >> course only happen after the release is done via this vote.
> >>
> >>
r the user’s convenience.
>
> Ralph
>
>> On Jul 26, 2022, at 6:25 PM, Robert Middleton wrote:
>>
>> The binaries won't show up under downloads.apache.org until actually
>> released(e.g. under repos/dist/release/logging/log4net). That can of
>> course
Where is the zip of the source? The ASF releases source code. Binaries are for
the user’s convenience.
Ralph
> On Jul 26, 2022, at 6:25 PM, Robert Middleton wrote:
>
> The binaries won't show up under downloads.apache.org until actually
> released(e.g. under repos/dist/release/log
gt; The binaries won't show up under downloads.apache.org until actually
> > released(e.g. under repos/dist/release/logging/log4net). That can of
> > course only happen after the release is done via this vote.
> >
> > I'll take a look at it in a bit just to validate th
I haven’t forgotten about this, but I may not be able to look at it until
Saturday.
Ralph
> On Jul 26, 2022, at 6:25 PM, Robert Middleton wrote:
>
> The binaries won't show up under downloads.apache.org until actually
> released(e.g. under repos/dist/release/logging/log4net
The binaries won't show up under downloads.apache.org until actually
released(e.g. under repos/dist/release/logging/log4net). That can of
course only happen after the release 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
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
for the bad responsivness
From: Davyd McColl
Sent: Wednesday, February 23, 2022 7:51 AM
To: Vladimir Vedeneev ; dev@logging.apache.org
Cc: Petker Denis 8BM3
Subject: *EXT* [Newsletter] Re: Re: [Newsletter] Re: log4net - performance hit
because UserName is fetched always
Hi Vladimir
(to clarify
Hi Vladimir
(to clarify, from here on "fixed" refers to being unchanging, not reverted from
a broken state, and much of this message is for my own benefit as there are
still large portions of log4net that I'm not well-acquainted with)
I believe you're on the right track here -
Again not sure if this is applicable to your case, there are some
discussions regarding UserName and performance in internet, like this one
(with sql appender specifics)
https://www.codewrecks.com/post/old/2015/03/bufferingappenderskeleton-performance-problem-in-log4net/
As a result they refer
ch log-event
as well.
Although we are not using username, I don’t see a way to avoid fetching it from
the system using the latest version of log4net.
If caching the username isn’t an option, my suggestion would be to get rid of
these lines from LoggingEvent.cs
// event properties
he problem?
Denis, can you elaborate on the use-case please? If your application never
impersonates, the value seems, to me, to have little value in logs, and if it
does impersonate,
then it should be updated. The edge case is multiple applications using the
same log4net configuratio
> there is no reason in printing the user name per log statement. However,
> > the ticket LOG4NET-205 has been raised by someone, who obviously was
> > interested in filtering log events by username?
> >
> > So what you mean technically is to retrieve the username once at st
> If we say, that the username isn't going to change for a process, I think
> there is no reason in printing the user name per log statement. However,
> the ticket LOG4NET-205 has been raised by someone, who obviously was
> interested in filtering log events by username?
>
>
10:22 AM
To: dev@logging.apache.org
Cc: Petker Denis 8BM3
Subject: *EXT* [Newsletter] RE: [Newsletter] Re: log4net - performance hit
because UserName is fetched always
Hi Denis
I would imagine that the use case is for shared logging config between
processes.
I think that the issue could be
t-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, February 22, 2022 10:22 AM
To: dev@logging.apache.org
Cc: Petker Denis 8BM3
Subject: *EXT* [Newsletter] RE: [Newsletter] Re: log4net - p
for a process, I think there
is no reason in printing the user name per log statement. However, the ticket
LOG4NET-205 has been raised by someone, who obviously was interested in
filtering log events by username?
So what you mean technically is to retrieve the username once at startup and
cache
Hi Davyd
Thanks for the quick response! Agreed, I also don't think, that the username
doesn't change for a process.
If we say, that the username isn't going to change for a process, I think there
is no reason in printing the user name per log statement. However, the ticket
LOG4NET-205 has
for a hastier release.
-d
On Feb 21 2022, at 7:22 pm, Denis Petker wrote:
>
> Hi all,
>
> we have upgraded the log4net version from 1.2.10 to the newest version 2.0.14
> and are now facing performace issues. I already have done some investigation
> looking at the log4net code.
> Wi
Hi all,
we have upgraded the log4net version from 1.2.10 to the newest version 2.0.14
and are now facing performace issues. I already have done some investigation
looking at the log4net code.
With the ticket LOG4NET-205<https://issues.apache.org/jira/browse/LOG4NET-205>
a change ha
(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 release log4net 2.0.14. Changelog is up
on
the
pre-release page at
https
e source zip are
>>>>>>> missing
>>>>>>>> copyright headers or shouldn’t even be included in the tarball (e.g.,
>>>>>>> the
>>>>>>>> appveyor config file probably isn’t necessary)
>>>>>>>
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 release log4net 2.0.14. Changelog is up
on
the
pre-release page at
https://github.com/apache
shouldn’t even be included in the tarball (e.g.,
>>>>> the
>>>>>> appveyor config file probably isn’t necessary)
>>>>>> - Not sure what old-log4net.snk.gpg is in there for, either.
>>>>>> - Gulp task source files missing headers
>>
gt;>>> appveyor config file probably isn’t necessary)
> >>>> - Not sure what old-log4net.snk.gpg is in there for, either.
> >>>> - Gulp task source files missing headers
> >>>> * Artifact signatures and sha512 hashes look good (checked with shasum
> >>&
config file probably isn’t necessary)
>>>> - Not sure what old-log4net.snk.gpg is in there for, either.
>>>> - Gulp task source files missing headers
>>>> * Artifact signatures and sha512 hashes look good (checked with shasum
>>>> which is the Per
; > - Gulp task source files missing headers
> > > * Artifact signatures and sha512 hashes look good (checked with shasum
> > > which is the Perl script version), contain appropriate LICENSE and
> > NOTICE
> > > (besides the outdated copyright year, but not
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 release log4net 2.0.14. Changelog is up on
> the
> >> pre-rele
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 release log4net
1 - 100 of 5553 matches
Mail list logo
