Re: [VOTE] Release Log4Net 2.0.9

[Ralph Goers]

And, FWIW, Nuget won’t let me register with my apache.org  
email address saying it can’t be a work or school email.

Ralph

> On Aug 21, 2020, at 4:46 PM, Ralph Goers  wrote:
> 
> This gets better and better. I was able to decrypt the file but the 
> credentials don’t work.  The Nuget.org  site says 
> “NuGet.org  password login in no longer supported. Please 
> use a Microsoft account to sign into NuGet gallery.”
> 
> Ralph
> 
>> On Aug 21, 2020, at 4:37 PM, Ralph Goers  wrote:
>> 
>> Going back through my old emails I see Dominik had the same problem in 2016. 
>> I forgot to update my files and now I see the instructions have changed.
>> 
>> Ralph
>> 
>>> On Aug 21, 2020, at 4:27 PM, Ralph Goers  wrote:
>>> 
>>> I figured out that the document is now at home.apache.org 
>>> . Unfortunately, that didn’t do me any good. gpg 
>>> -d is failing with “No secret key”. That doesn’t seem too surprising since 
>>> my key wasn’t used to sign the document.
>>> 
>>> Ralph
>>> 
 On Aug 21, 2020, at 3:53 PM, Ralph Goers  
 wrote:
 
 Dominik,
 
 The README file says that the keys can be found at 
 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, Dominik 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 in the private repos of logging
> pmc. Most members of the pmc should 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 a look at what's at the url you posted, I have ideas on how to
>> streamline future releases, so the next time I'm in that area, I'm
>> definitely implementing those ideas. I don't see changes to the Release
>> Notes area -- if I were to try to streamline that into a release, would a
>> CHANGELOG file be useful? Or is there a better way?
>> 
>> -d
>> On 2020/08/16 23:26:07, Matt Sicker  wrote:
>> I committed them to dist already. I don't know how long we should wait
>> for any mirroring to catch up, though on my end, I see updated
>> artifacts on https://downloads.apache.org/logging/log4net/ other than
>> the release notes.
>> 
>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>> 
>>> +1 to that!
>>> 
>>> Let me know when these are published. I can update the web site 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'll make changes to the automated build to affect all changes you
>> have
> made (and perhaps will make) automatically to future releases for the
>> next
> release. Apologies for making this more difficult than it needs to be
>> (:
> 
> -d
> 
> 
> On August 16, 2020 20:37:01 Matt Sicker wrote:
> 
>> Just a simple copy of the LICENSE and NOTICE file into the binaries
>> zip, and a rename of the files to include "apache" in the name. I've
>> uploaded them to dist along with updating the KEYS file for log4net,
>> though that should probably be merged together with the project-wide
>> KEYS file in the parent directory. There's an outdated README.html in
>> the directory still containing the old release notes, but we can
>> address that next.
>> 
>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>> 
>>> One issue I found in one of the artifacts that I can address before
>>> uploading since it wasn't signed is the binaries zip is missing the
>>> LICENSE file. I'm not sure if there's a standard way to include that
>>> in the nupkg file, but I did see that in its metadata, it explicitly
>>> says the code is Apache2 licensed at least.
>>> 
>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
 
 I'll sign and publish the artifacts today.
 
 On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
> 
> Thanks Remko. That makes 3 +1 votes from PMC members.
> 
> Ralph
> 
>> On Aug 3, 2020, at 

Re: [VOTE] Release Log4Net 2.0.9

[Ralph Goers]

This gets better and better. I was able to decrypt the file but the credentials 
don’t work.  The Nuget.org  site says “NuGet.org 
 password login in no longer supported. Please use a 
Microsoft account to sign into NuGet gallery.”

Ralph

> On Aug 21, 2020, at 4:37 PM, Ralph Goers  wrote:
> 
> Going back through my old emails I see Dominik had the same problem in 2016. 
> I forgot to update my files and now I see the instructions have changed.
> 
> Ralph
> 
>> On Aug 21, 2020, at 4:27 PM, Ralph Goers  wrote:
>> 
>> I figured out that the document is now at home.apache.org 
>> . Unfortunately, that didn’t do me any good. gpg -d 
>> is failing with “No secret key”. That doesn’t seem too surprising since my 
>> key wasn’t used to sign the document.
>> 
>> Ralph
>> 
>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers  wrote:
>>> 
>>> Dominik,
>>> 
>>> The README file says that the keys can be found at 
>>> 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, Dominik 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 in the private repos of logging
 pmc. Most members of the pmc should 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 a look at what's at the url you posted, I have ideas on how to
> streamline future releases, so the next time I'm in that area, I'm
> definitely implementing those ideas. I don't see changes to the Release
> Notes area -- if I were to try to streamline that into a release, would a
> CHANGELOG file be useful? Or is there a better way?
> 
> -d
> On 2020/08/16 23:26:07, Matt Sicker  wrote:
> I committed them to dist already. I don't know how long we should wait
> for any mirroring to catch up, though on my end, I see updated
> artifacts on https://downloads.apache.org/logging/log4net/ other than
> the release notes.
> 
> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>> 
>> +1 to that!
>> 
>> Let me know when these are published. I can update the web site 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'll make changes to the automated build to affect all changes you
> have
 made (and perhaps will make) automatically to future releases for the
> next
 release. Apologies for making this more difficult than it needs to be
> (:
 
 -d
 
 
 On August 16, 2020 20:37:01 Matt Sicker wrote:
 
> Just a simple copy of the LICENSE and NOTICE file into the binaries
> zip, and a rename of the files to include "apache" in the name. I've
> uploaded them to dist along with updating the KEYS file for log4net,
> though that should probably be merged together with the project-wide
> KEYS file in the parent directory. There's an outdated README.html in
> the directory still containing the old release notes, but we can
> address that next.
> 
> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>> 
>> One issue I found in one of the artifacts that I can address before
>> uploading since it wasn't signed is the binaries zip is missing the
>> LICENSE file. I'm not sure if there's a standard way to include that
>> in the nupkg file, but I did see that in its metadata, it explicitly
>> says the code is Apache2 licensed at least.
>> 
>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>>> 
>>> I'll sign and publish the artifacts today.
>>> 
>>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
 
 Thanks Remko. That makes 3 +1 votes from PMC members.
 
 Ralph
 
> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
> 
> +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 

Re: [VOTE] Release Log4Net 2.0.9

[Ralph Goers]

Going back through my old emails I see Dominik had the same problem in 2016. I 
forgot to update my files and now I see the instructions have changed.

Ralph

> On Aug 21, 2020, at 4:27 PM, Ralph Goers  wrote:
> 
> I figured out that the document is now at home.apache.org 
> . Unfortunately, that didn’t do me any good. gpg -d 
> is failing with “No secret key”. That doesn’t seem too surprising since my 
> key wasn’t used to sign the document.
> 
> Ralph
> 
>> On Aug 21, 2020, at 3:53 PM, Ralph Goers  wrote:
>> 
>> Dominik,
>> 
>> The README file says that the keys can be found at 
>> 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, Dominik 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 in the private repos of logging
>>> pmc. Most members of the pmc should 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 a look at what's at the url you posted, I have ideas on how to
 streamline future releases, so the next time I'm in that area, I'm
 definitely implementing those ideas. I don't see changes to the Release
 Notes area -- if I were to try to streamline that into a release, would a
 CHANGELOG file be useful? Or is there a better way?
 
 -d
 On 2020/08/16 23:26:07, Matt Sicker  wrote:
 I committed them to dist already. I don't know how long we should wait
 for any mirroring to catch up, though on my end, I see updated
 artifacts on https://downloads.apache.org/logging/log4net/ other than
 the release notes.
 
 On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
> 
> +1 to that!
> 
> Let me know when these are published. I can update the web site 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'll make changes to the automated build to affect all changes you
 have
>>> made (and perhaps will make) automatically to future releases for the
 next
>>> release. Apologies for making this more difficult than it needs to be
 (:
>>> 
>>> -d
>>> 
>>> 
>>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>> 
 Just a simple copy of the LICENSE and NOTICE file into the binaries
 zip, and a rename of the files to include "apache" in the name. I've
 uploaded them to dist along with updating the KEYS file for log4net,
 though that should probably be merged together with the project-wide
 KEYS file in the parent directory. There's an outdated README.html in
 the directory still containing the old release notes, but we can
 address that next.
 
 On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
> 
> One issue I found in one of the artifacts that I can address before
> uploading since it wasn't signed is the binaries zip is missing the
> LICENSE file. I'm not sure if there's a standard way to include that
> in the nupkg file, but I did see that in its metadata, it explicitly
> says the code is Apache2 licensed at least.
> 
> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>> 
>> I'll sign and publish the artifacts today.
>> 
>> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>>> 
>>> Thanks Remko. That makes 3 +1 votes from PMC members.
>>> 
>>> Ralph
>>> 
 On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
 
 +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
> wrote:
>> 
>> Can other PMC members please review this? It has been more
 than 72
> hours.
>> 
>> Ralph
>> 
>>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
> wrote:
>>> 
>>> Hi all, I've never done this before, so bear with me if I
 fluff it:
>>> 
>>> This is a proposed vote to release 

Re: [VOTE] Release Log4Net 2.0.9

[Ralph Goers]

I figured out that the document is now at home.apache.org 
. Unfortunately, that didn’t do me any good. gpg -d is 
failing with “No secret key”. That doesn’t seem too surprising since my key 
wasn’t used to sign the document.

Ralph

> On Aug 21, 2020, at 3:53 PM, Ralph Goers  wrote:
> 
> Dominik,
> 
> The README file says that the keys can be found at 
> 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, Dominik 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 in the private repos of logging
>> pmc. Most members of the pmc should 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 a look at what's at the url you posted, I have ideas on how to
>>> streamline future releases, so the next time I'm in that area, I'm
>>> definitely implementing those ideas. I don't see changes to the Release
>>> Notes area -- if I were to try to streamline that into a release, would a
>>> CHANGELOG file be useful? Or is there a better way?
>>> 
>>> -d
>>> On 2020/08/16 23:26:07, Matt Sicker  wrote:
>>> I committed them to dist already. I don't know how long we should wait
>>> for any mirroring to catch up, though on my end, I see updated
>>> artifacts on https://downloads.apache.org/logging/log4net/ other than
>>> the release notes.
>>> 
>>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
 
 +1 to that!
 
 Let me know when these are published. I can update the web site 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'll make changes to the automated build to affect all changes you
>>> have
>> made (and perhaps will make) automatically to future releases for the
>>> next
>> release. Apologies for making this more difficult than it needs to be
>>> (:
>> 
>> -d
>> 
>> 
>> On August 16, 2020 20:37:01 Matt Sicker wrote:
>> 
>>> Just a simple copy of the LICENSE and NOTICE file into the binaries
>>> zip, and a rename of the files to include "apache" in the name. I've
>>> uploaded them to dist along with updating the KEYS file for log4net,
>>> though that should probably be merged together with the project-wide
>>> KEYS file in the parent directory. There's an outdated README.html in
>>> the directory still containing the old release notes, but we can
>>> address that next.
>>> 
>>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
 
 One issue I found in one of the artifacts that I can address before
 uploading since it wasn't signed is the binaries zip is missing the
 LICENSE file. I'm not sure if there's a standard way to include that
 in the nupkg file, but I did see that in its metadata, it explicitly
 says the code is Apache2 licensed at least.
 
 On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
> 
> I'll sign and publish the artifacts today.
> 
> On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>> 
>> Thanks Remko. That makes 3 +1 votes from PMC members.
>> 
>> Ralph
>> 
>>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>>> 
>>> +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
 wrote:
> 
> Can other PMC members please review this? It has been more
>>> than 72
 hours.
> 
> Ralph
> 
>> On Jul 30, 2020, at 11:17 PM, Davyd McColl
 wrote:
>> 
>> 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/34063235/artifacts
>> Source can be checked out from
 

Re: [VOTE] Release Log4Net 2.0.9

[Ralph Goers]

Dominik,

The README file says that the keys can be found at 
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, Dominik 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 in the private repos of logging
> pmc. Most members of the pmc should 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 a look at what's at the url you posted, I have ideas on how to
>> streamline future releases, so the next time I'm in that area, I'm
>> definitely implementing those ideas. I don't see changes to the Release
>> Notes area -- if I were to try to streamline that into a release, would a
>> CHANGELOG file be useful? Or is there a better way?
>> 
>> -d
>> On 2020/08/16 23:26:07, Matt Sicker  wrote:
>> I committed them to dist already. I don't know how long we should wait
>> for any mirroring to catch up, though on my end, I see updated
>> artifacts on https://downloads.apache.org/logging/log4net/ other than
>> the release notes.
>> 
>> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>> 
>>> +1 to that!
>>> 
>>> Let me know when these are published. I can update the web site 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'll make changes to the automated build to affect all changes you
>> have
> made (and perhaps will make) automatically to future releases for the
>> next
> release. Apologies for making this more difficult than it needs to be
>> (:
> 
> -d
> 
> 
> On August 16, 2020 20:37:01 Matt Sicker wrote:
> 
>> Just a simple copy of the LICENSE and NOTICE file into the binaries
>> zip, and a rename of the files to include "apache" in the name. I've
>> uploaded them to dist along with updating the KEYS file for log4net,
>> though that should probably be merged together with the project-wide
>> KEYS file in the parent directory. There's an outdated README.html in
>> the directory still containing the old release notes, but we can
>> address that next.
>> 
>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>> 
>>> One issue I found in one of the artifacts that I can address before
>>> uploading since it wasn't signed is the binaries zip is missing the
>>> LICENSE file. I'm not sure if there's a standard way to include that
>>> in the nupkg file, but I did see that in its metadata, it explicitly
>>> says the code is Apache2 licensed at least.
>>> 
>>> On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
 
 I'll sign and publish the artifacts today.
 
 On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
> 
> Thanks Remko. That makes 3 +1 votes from PMC members.
> 
> Ralph
> 
>> On Aug 3, 2020, at 2:12 PM, Remko Popma wrote:
>> 
>> +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
>>> wrote:
 
 Can other PMC members please review this? It has been more
>> than 72
>>> hours.
 
 Ralph
 
> On Jul 30, 2020, at 11:17 PM, Davyd McColl
>>> wrote:
> 
> 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/34063235/artifacts
> Source can be checked out from
>>> https://github.com/fluffynuts/logging-log4net/logging-log4net,
>> tag rel/
>>> 2.0.9. I can't push tags to the upstream, but this tag is
>> exactly the
>>> same commit as the last in the PR mentioned above, which was
>>> accepted into
>>> master a few days ago.
> 
> Please check out the artifacts & if everyone is ok with
>> what's there,
>>> please can someone with the rights to publish to nuget do so.

Re: [VOTE] Release Log4Net 2.0.9

[Ralph Goers]

I tried building the web site using mvn site but it seems the site artifacts 
were moved. How do you propose to update the web site for this release?

Ralph

> On Aug 17, 2020, at 12:36 PM, Davyd McColl  wrote:
> 
> I would imagine that this would have to either happen on Apache infra or be a 
> GH action administered by someone with uber rights, though, yes, this is a 
> good option. I don't have all the working pieces in my flows, but it would be 
> convenient for my packages to have a similar mechanism, so if this is 
> something the PMC would be interested in, I could play-test it against 
> PeanutButter.* before proposing an automated solution?
> 
> -d
> 
> 
> On August 17, 2020 20:07:34 Dominik Psenner  wrote:
> 
>> Is there an option to trust a ci machine and automate the publish with a
>> push of a tag after a successful 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, is to allow me to
>>> publish. My nuget login is done via Microsoft credentials for
>>> dav...@gmail.com, and is secured by 2FA, so the only real risk is how
>>> dodgy
>>> I am (:
>>> 
>>> If it's of interest to anyone, my profile is at
>>> https://www.nuget.org/profiles/davydm
>>> 
>>> -d
>>> 
>>> 
>>> On August 17, 2020 18:46:50 Dominik 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 in the private repos of
>>> logging
>>> > pmc. Most members of the pmc should 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 a look at what's at the url you posted, I have ideas on how to
>>> >> streamline future releases, so the next time I'm in that area, I'm
>>> >> definitely implementing those ideas. I don't see changes to the Release
>>> >> Notes area -- if I were to try to streamline that into a release, would
>>> a
>>> >> CHANGELOG file be useful? Or is there a better way?
>>> >>
>>> >> -d
>>> >> On 2020/08/16 23:26:07, Matt Sicker  wrote:
>>> >> I committed them to dist already. I don't know how long we should wait
>>> >> for any mirroring to catch up, though on my end, I see updated
>>> >> artifacts on https://downloads.apache.org/logging/log4net/ other than
>>> >> the release notes.
>>> >>
>>> >> On Sun, 16 Aug 2020 at 15:09, Ralph Goers wrote:
>>> >> >
>>> >> > +1 to that!
>>> >> >
>>> >> > Let me know when these are published. I can update the web site 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'll make changes to the automated build to affect all changes you
>>> >> have
>>> >> > >> made (and perhaps will make) automatically to future releases for
>>> the
>>> >> next
>>> >> > >> release. Apologies for making this more difficult than it needs to
>>> be
>>> >> (:
>>> >> > >>
>>> >> > >> -d
>>> >> > >>
>>> >> > >>
>>> >> > >> On August 16, 2020 20:37:01 Matt Sicker wrote:
>>> >> > >>
>>> >> > >>> Just a simple copy of the LICENSE and NOTICE file into the
>>> binaries
>>> >> > >>> zip, and a rename of the files to include "apache" in the name.
>>> I've
>>> >> > >>> uploaded them to dist along with updating the KEYS file for
>>> log4net,
>>> >> > >>> though that should probably be merged together with the
>>> project-wide
>>> >> > >>> KEYS file in the parent directory. There's an outdated
>>> README.html in
>>> >> > >>> the directory still containing the old release notes, but we can
>>> >> > >>> address that next.
>>> >> > >>>
>>> >> > >>> On Sun, 16 Aug 2020 at 13:12, Matt Sicker wrote:
>>> >> > 
>>> >> >  One issue I found in one of the artifacts that I can address
>>> before
>>> >> >  uploading since it wasn't signed is the binaries zip is missing
>>> the
>>> >> >  LICENSE file. I'm not sure if there's a standard way to include
>>> that
>>> >> >  in the nupkg file, but I did see that in its metadata, it
>>> explicitly
>>> >> >  says the code is Apache2 licensed at least.
>>> >> > 
>>> >> >  On Sun, 16 Aug 2020 at 13:03, Matt Sicker wrote:
>>> >> > >
>>> >> > > I'll sign and publish the artifacts today.
>>> >> > >
>>> >> > > On Mon, 3 Aug 2020 at 17:43, Ralph Goers wrote:
>>> >> > >>
>>> 

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

[Ralph Goers]

I tried running mvn site for log4cxx and it failed. Since the pom is still 
0.11.0-SNAPSHOT everything that refers to the version would be wrong. If I just 
patch the download page then the changes page won’t reflect whatever was done 
in 0.11.0. I also noticed that the source links are pointing to gitbox. Is that 
desired or should they point to GitHub?

At this point I am not sure how to update the site.

Thoughts?

Ralph

> On Aug 21, 2020, at 2:18 PM, Ralph Goers  wrote:
> 
> I have moved the files to the release folder. I will look at updating the web 
> site.
> 
> Ralph
> 
>> On Aug 18, 2020, at 4:49 PM, Ralph Goers  wrote:
>> 
>> I’ll take care of it.
>> 
>> Ralph
>> 
>>> On Aug 18, 2020, at 3:46 PM, Robert Middleton  wrote:
>>> 
>>> By my count at this point, that means we have 3 binding +1 votes from
>>> Ralph, Christian, Remko; and +1 votes from Thorsten and Stephen.
>>> 
>>> Ralph, do you want to upload to the releases repo with the fix for the .sha
>>> file, or do you want me to do that?(it is a SHA-512, it's just named
>>> incorrectly)
>>> 
>>> -Robert Middleton
>>> 
>>> On Mon, Aug 17, 2020 at 5:47 AM Stephen Webb  wrote:
>>> 
 I am using a recent version in production Ubuntu servers, so it is
 definitely release ready.
 +1
 
 On Mon, Aug 17, 2020, 7:27 PM Christian Grobmeier 
 wrote:
 
> Hello,
> 
> I am not an expert on c++ or something, but I looked on the content, read
> this thread and think it is safe to release this. However, my hope is
 that
> in future more competent cxx devs than me would check it :)
> 
> I vote +1 also
> 
> Cheers,
> Christian
> 
> On Mon, Aug 17, 2020, at 08:08, Ralph Goers wrote:
>> I noticed that the files have she and md5 files. We are not supposed to
>> use either of these any more and only use sha512. I can fix that.
>> 
>> I vote +1
>> 
>> Ralph
>> 
>> 
>> 
>> 
>>> On Aug 9, 2020, at 10:24 AM, Robert Middleton 
> wrote:
>>> 
>>> I've run through the release of log4cxx 0.11.0.  There's still
> something
>>> strange about how it all works(mostly due to the tooling of shell
>>> script/maven/ant/cmake/autotools).  However, I do believe that I
 have a
>>> workable release at this point.  A quick note on the release: I did
 the
>>> 'mvn release:prepare' manually, which is where these artifacts come
> from;
>>> running through the 'mvn release:perform' causes the generated files
> to be
>>> -SNAPSHOT versioned, instead of 0.11.0.  This means that the version
> of the
>>> pom.xml in the tag is still 0.11.0-SNAPSHOT, but since maven isn't
> really
>>> used to build I don't think this will be an issue.
>>> 
>>> Artifacts uploaded here:
>>> https://dist.apache.org/repos/dist/dev/logging/log4cxx/
>>> tag: https://github.com/apache/logging-log4cxx/tree/v0.11.0-RC2
>>> 
>>> The artifacts are signed, although I still need to send my key to
 Matt
> so
>>> he can import it into the logging KEYS file.
>>> 
>>> -Robert Middleton
>> 
>> 
>> 
> 
 
>> 
>> 
>> 
> 
> 
> 

Re: [VOTE] [log4xx] Release log4cxx 0.11.0

[Ralph Goers]

I have moved the files to the release folder. I will look at updating the web 
site.

Ralph

> On Aug 18, 2020, at 4:49 PM, Ralph Goers  wrote:
> 
> I’ll take care of it.
> 
> Ralph
> 
>> On Aug 18, 2020, at 3:46 PM, Robert Middleton  wrote:
>> 
>> By my count at this point, that means we have 3 binding +1 votes from
>> Ralph, Christian, Remko; and +1 votes from Thorsten and Stephen.
>> 
>> Ralph, do you want to upload to the releases repo with the fix for the .sha
>> file, or do you want me to do that?(it is a SHA-512, it's just named
>> incorrectly)
>> 
>> -Robert Middleton
>> 
>> On Mon, Aug 17, 2020 at 5:47 AM Stephen Webb  wrote:
>> 
>>> I am using a recent version in production Ubuntu servers, so it is
>>> definitely release ready.
>>> +1
>>> 
>>> On Mon, Aug 17, 2020, 7:27 PM Christian Grobmeier 
>>> wrote:
>>> 
 Hello,
 
 I am not an expert on c++ or something, but I looked on the content, read
 this thread and think it is safe to release this. However, my hope is
>>> that
 in future more competent cxx devs than me would check it :)
 
 I vote +1 also
 
 Cheers,
 Christian
 
 On Mon, Aug 17, 2020, at 08:08, Ralph Goers wrote:
> I noticed that the files have she and md5 files. We are not supposed to
> use either of these any more and only use sha512. I can fix that.
> 
> I vote +1
> 
> Ralph
> 
> 
> 
> 
>> On Aug 9, 2020, at 10:24 AM, Robert Middleton 
 wrote:
>> 
>> I've run through the release of log4cxx 0.11.0.  There's still
 something
>> strange about how it all works(mostly due to the tooling of shell
>> script/maven/ant/cmake/autotools).  However, I do believe that I
>>> have a
>> workable release at this point.  A quick note on the release: I did
>>> the
>> 'mvn release:prepare' manually, which is where these artifacts come
 from;
>> running through the 'mvn release:perform' causes the generated files
 to be
>> -SNAPSHOT versioned, instead of 0.11.0.  This means that the version
 of the
>> pom.xml in the tag is still 0.11.0-SNAPSHOT, but since maven isn't
 really
>> used to build I don't think this will be an issue.
>> 
>> Artifacts uploaded here:
>> https://dist.apache.org/repos/dist/dev/logging/log4cxx/
>> tag: https://github.com/apache/logging-log4cxx/tree/v0.11.0-RC2
>> 
>> The artifacts are signed, although I still need to send my key to
>>> Matt
 so
>> he can import it into the logging KEYS file.
>> 
>> -Robert Middleton
> 
> 
> 
 
>>> 
> 
> 
> 

Re: GitHub Actions CI failure on release-2.x

[Matt Sicker]

I’ve been modifying build settings in master lately that haven’t been
merged back to this branch. I’d assume there’s a difference in the pom file
here. I’ll take a closer look later today.

On Fri, Aug 21, 2020 at 04:31 Volkan Yazıcı  wrote:

> GitHub Actions CI build is failing on release-2.x
>
>  with the
>
> following error:
>
>
>
> [ERROR] Failed to execute goal
>
> org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on
>
> project log4j-api-java9: Misconfigured toolchains. Non-existing JDK home
>
> configuration at
>
> /Users/runner/work/logging-log4j2/logging-log4j2/${env.JAVA_HOME_8_X64} ->
>
> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>
> goal org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain
>
> (default) on project log4j-api-java9: Misconfigured toolchains.
>
>
>
> I am confused and clueless, since the very same [GitHub Actions]
>
> configuration works perfectly well on "master". Any ideas? Matt?
>
> --
Matt Sicker 

GitHub Actions CI failure on release-2.x

[Volkan Yazıcı]

GitHub Actions CI build is failing on release-2.x
 with the
following error:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain (default) on
project log4j-api-java9: Misconfigured toolchains. Non-existing JDK home
configuration at
/Users/runner/work/logging-log4j2/logging-log4j2/${env.JAVA_HOME_8_X64} ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain
(default) on project log4j-api-java9: Misconfigured toolchains.

I am confused and clueless, since the very same [GitHub Actions]
configuration works perfectly well on "master". Any ideas? Matt?