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.0 support from community
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
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 hashing, and needed a tag to work
>
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
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
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:
>
> Ralph,
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 doc somewhere that someone new
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 with tags )
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:
>>>
>>>> Ok, log4net 2.0.9 is up on nug
cts 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
> associated download_log4net.html
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
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:
>
>
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
-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, Davyd Mc
alph
> 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 understand what maven is doing, s
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 (target html file
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 home directory
, 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
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:
>
>
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
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
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
s what 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
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
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 AM, Do
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 in the
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 trusted
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.
Having
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 the url you posted, I have ideas
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'll make changes to t
t; > 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
> > >> wrote:
> > >>>
&g
, 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 valuable
, 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 account (default in my mail client)
-d
On 2020
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 proposed vote
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:
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
. 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, though it's either:
> 1.
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_ docker image (and batch file) which builds log4net fine
>
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
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 up to either integrating
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-compilation, but older
targets
s.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 with Apache
Infra?
> &
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, Davyd McColl wrote
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
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
ure/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 McColl wrote:
A short update (no
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,
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
://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 (which I will have to do
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
> node-based bu
;
> 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 Jenkins, but that is not a requirement.
>
> Ralph
>
> > On Apr 7, 2020,
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 -- not sure where though:
&
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 promising, and I'm aware that I'm probably being
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 publishing under a
different package name is probably
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 been told that the team has been looking for outside help for
around 2
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
101 - 156 of 156 matches
Mail list logo
