[VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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 to releas

Re: [VOTE] Release Log4Net 2.0.9

So far it looks good (though I'm not a .net developer, so I can't speak from that side). There's one more thing we need from this to make it a proper release. You'll need to add a GPG signature for the artifacts as well. We'll need to import your signing key to https://downloads.apache.org/logging/

Re: [VOTE] Release Log4Net 2.0.9

Having never signed release artifacts before, I'm likely to Do It Wrong. Is there any Signing For Dummies you could recommend to get going on the right foot? -d On August 2, 2020 21:31:43 Matt Sicker wrote: So far it looks good (though I'm not a .net developer, so I can't speak from that s

Re: [VOTE] Release Log4Net 2.0.9

Here's some info for you: https://infra.apache.org/release-signing.html And some general info about release publishing: https://infra.apache.org/release-publishing.html On Sun, 2 Aug 2020 at 14:47, Davyd McColl wrote: > > Having never signed release artifacts before, I'm likely to Do It Wrong.

Re: [VOTE] Release Log4Net 2.0.9

I am going to vote +1 (binding) on this release. Although it does need to be signed I am comfortable with either Matt or myself signing it before it is uploaded as Davyd’s signing key isn’t going to be signed by anyone if he has never had a key before. One of us is going to have to publish this

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

+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

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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: > > > >

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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 diff

Re: [VOTE] Release Log4Net 2.0.9

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 o

Re: [VOTE] Release Log4Net 2.0.9

+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

Re: [VOTE] Release Log4Net 2.0.9

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 m

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

The release notes are generated from the README.html file in the dist area. I'm not sure where they're generated from, but some sort of changelog file to go alongside the artifacts could be helpful here. Otherwise, we'd typically only worry about the download links on the logging.apache.org site.

Re: [VOTE] Release Log4Net 2.0.9

The nuget.org question is probably of the highest priority - that's how most people are going to get any .net package release. If it's not on nuget.org, it might as well not be released. Any idea who would know about releasing there? Is there someone I can bother? -d On August 17, 2020 18:08

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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/profil

Re: [VOTE] Release Log4Net 2.0.9

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,

Re: [VOTE] Release Log4Net 2.0.9

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 thi

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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 gue

Re: [VOTE] Release Log4Net 2.0.9

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 Goe

Re: [VOTE] Release Log4Net 2.0.9

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 >

Re: [VOTE] Release Log4Net 2.0.9

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

Re: [VOTE] Release Log4Net 2.0.9

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. Th

Re: [VOTE] Release Log4Net 2.0.9

Hi I recall that we were forced to transform the nuget account Apache.Logging ( https://www.nuget.org/profiles/Apache.Logging) from a personal account into an organization. I am currently the only member and administrator of that organization. Please share with me (may also be in private) the nuge

Re: [VOTE] Release Log4Net 2.0.9

I know I'm quite new, but I'm happy to push approved packages. My Microsoft account for nuget is this email address (dav...@gmail.com) -d On August 22, 2020 19:46:45 Dominik Psenner wrote: Hi I recall that we were forced to transform the nuget account Apache.Logging ( https://www.nuget.org

Re: [VOTE] Release Log4Net 2.0.9

Apparently it cant be the email but must be the nuget accounts username, apologies. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Sat, Aug 22, 2020, 20:39 Davyd McColl wrote: > I know I'm quite new, but I'm happy to push approved packages. My > Microsoft >

Re: [VOTE] Release Log4Net 2.0.9

Oh ok, well, mine is davydm (: -d On August 22, 2020 20:49:59 Dominik Psenner wrote: Apparently it cant be the email but must be the nuget accounts username, apologies. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Sat, Aug 22, 2020, 20:39 Davyd McColl

Re: [VOTE] Release Log4Net 2.0.9

Davyd, I added you as a collaborator. This should grant you the privilege to manage packages. You can now submit new and update or unlist existing packages. It would be great to have at least one other member of the pmc listed as administrator. The following documents the matrix of permissions. No

Re: [VOTE] Release Log4Net 2.0.9

Thanks Dominik Are there any objections to me pushing the 2.0.9 package that had been approved and uploaded to https://downloads.apache.org/logging/log4net/ to nuget.org? -d On August 23, 2020 09:59:02 Dominik Psenner wrote: Davyd, I added you as a collaborator. This should grant you the

Re: [VOTE] Release Log4Net 2.0.9

There can’t be. That is 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.org/logging/log4net/ to > nuget.o

Re: [VOTE] Release Log4Net 2.0.9

Yes, please go ahead and finish the release. The PMC approved this during our release vote. :) On Sun, 23 Aug 2020 at 10:22, Apache wrote: > > There can’t be. That is what the release vote was for. > > Ralph > > > On Aug 23, 2020, at 1:02 AM, Davyd McColl wrote: > > > > Thanks Dominik > > > > A

Re: [VOTE] Release Log4Net 2.0.9

Ok, log4net 2.0.9 is up on nuget.org (:  Thanks for all the help (: -d On 2020/08/23 19:13:36, Matt Sicker wrote: Yes, please go ahead and finish the release. The PMC approved this during our release vote. :) On Sun, 23 Aug 2020 at 10:22, Apache wrote: > > There can’t be. That is what the rele

Re: [VOTE] Release Log4Net 2.0.9

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 nuget.org (: > > > > Thanks for all the help (: > > > > -d > > > > On 2020/08/23 19:13:36, Matt Sicker wrote: > > Yes, pl

Re: [VOTE] Release Log4Net 2.0.9

Well done, everyone! 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: > > > Ok, log4net 2.0.9 is up on nuget.org (: > > > > > > > > Thanks

Re: [VOTE] Release Log4Net 2.0.9

The release isn’t done yet. The web site still reflects 2.0.8. Release announcements can’t be sent out until that is updated. Ralph > On Aug 24, 2020, at 2:45 PM, Remko Popma wrote: > > Well done, everyone! > > On Mon, Aug 24, 2020 at 10:43 PM Matt Sicker wrote: > >> Thanks again for mana

Re: [VOTE] Release Log4Net 2.0.9

I also just noticed that the git repo has no tag to represent 2.0.9. Without a tag essentially there is no release. Ralph > On Aug 24, 2020, at 3:27 PM, Ralph Goers wrote: > > The release isn’t done yet. The web site still reflects 2.0.8. Release > announcements can’t be sent out until that

Re: [VOTE] Release Log4Net 2.0.9

Hi Ralph The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously forgot to push with tags ): I've updated the source files for the site: - removed the mirror references - updated the links for 2.0.9 - updated the link to point to the html instead of the cgi I've also update

Re: [VOTE] Release Log4Net 2.0.9

Unfortunately the staging and release locations for the release artifacts are still using s not. But everything else is now in git. So in a release you should publish the web site to the asf-staging branch of the site repo and publish the artifacts to the dev location of the SVN dist repo. Once

Re: [VOTE] Release Log4Net 2.0.9

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 like me can follow for this? I'm just wasting your time here. -d On 2020/09/02 09:34:23, Apache wrote: Unfortunately the staging and release locations for th

Re: [VOTE] Release Log4Net 2.0.9

Subversion is still used for publishing release artifacts. The previous Subversion-based system for publishing the website itself has been migrated to git. Without using git-lfs, I don't see us migrating from svn to git for release distribution for quite some time (svn seems better suited for archi

Re: [VOTE] Release Log4Net 2.0.9

Ralph, I've updated apache/logging-log4net-site#asf-staging with the latest build artifacts from the apache/logging-log4net repo, please validate when you have time. Matt, I don't think I have access to push binary artifacts -- and, if I do, I don't know where (I'm quite sure Ralph did that for

Re: [VOTE] Release Log4Net 2.0.9

The release repository is only writable by PMC members. You won’t have to worry about that until then. :) On Thu, Sep 3, 2020 at 01:01 Davyd McColl wrote: > Ralph, I've updated apache/logging-log4net-site#asf-staging with the > latest build artifacts from the apache/logging-log4net repo, please

Re: [VOTE] Release Log4Net 2.0.9

OK, I’ve looked at http://logging.staged.apache.org/log4net. The download page still doesn’t look correct. 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 variabl

Re: [VOTE] Release Log4Net 2.0.9

Hi Ralph Sorry for wasting your time. I stupidly fixed up some of the the site in the SVN tree last time, and then re-generated before commiting to the github site, so it was still in a 1/2 state and I guess I was looking at the wrong thing in my browser when I checked ): I've updated again an

Re: [VOTE] Release Log4Net 2.0.9

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 fixed up some of the the site in the > SVN tree last time,

Re: [VOTE] Release Log4Net 2.0.9

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 fix