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 me last time, tho I'll need to understand better at some point so as to be less of a PITA); at least I understand now that the SVN repo for the logging site is deprecated and the new place I should be putting generated site material is as above (apache/logging-log4net-site#asf-staging) -d On 2020/09/02 17:01:15, Matt Sicker wrote: 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 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 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 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 they are > approved they can be published. You should have permission to publish the web > site already. > > I will try to verify your changes tomorrow. > > Ralph > > > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote: > > > > Hi Ralph > > > > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and > > obviously forgot to push 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 updated the README in the project to take out the dormant status > > commentary. > > > > Please review & update the live site if you're happy. > > > > Previously, as I understand it, the point of the SVN staging area was to > > provide built artifacts for the website. Since that's not in play any more, > > I was wondering how that's going to happen now? Someone will have to build > > before pushing. If you'd like, I could add the target folder that is built > > into git so that it's just a matter of copying files. > > > > I've also added an npm script around building the site, which checks if you > > have maven available & builds if possible -- perhaps this makes it easier > > for the next new person (: > > > > -d > > > > On 2020/09/02 05:20:50, Ralph Goers wrote: > > 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 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 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, 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 > > > >>> > > > >>> 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 > > privilege > > > to manage packages. You can now submit new and update or unlist > > existing > > > packages. > > > > > > It would be great to have at leas
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 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 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 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 they are > approved they can be published. You should have permission to publish the web > site already. > > I will try to verify your changes tomorrow. > > Ralph > > > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote: > > > > Hi Ralph > > > > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and > > obviously forgot to push 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 updated the README in the project to take out the dormant status > > commentary. > > > > Please review & update the live site if you're happy. > > > > Previously, as I understand it, the point of the SVN staging area was to > > provide built artifacts for the website. Since that's not in play any more, > > I was wondering how that's going to happen now? Someone will have to build > > before pushing. If you'd like, I could add the target folder that is built > > into git so that it's just a matter of copying files. > > > > I've also added an npm script around building the site, which checks if you > > have maven available & builds if possible -- perhaps this makes it easier > > for the next new person (: > > > > -d > > > > On 2020/09/02 05:20:50, Ralph Goers wrote: > > 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 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 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, 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 > > > >>> > > > >>> 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 > > 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. > > Note that > > > the amount of administrative tasks should be very 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
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 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 they are approved they can be published. You should have permission to publish the web site already. I will try to verify your changes tomorrow. Ralph > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote: > > Hi Ralph > > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously > forgot to push 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 updated the README in the project to take out the dormant status > commentary. > > Please review & update the live site if you're happy. > > Previously, as I understand it, the point of the SVN staging area was to > provide built artifacts for the website. Since that's not in play any more, I > was wondering how that's going to happen now? Someone will have to build > before pushing. If you'd like, I could add the target folder that is built > into git so that it's just a matter of copying files. > > I've also added an npm script around building the site, which checks if you > have maven available & builds if possible -- perhaps this makes it easier for > the next new person (: > > -d > > On 2020/09/02 05:20:50, Ralph Goers wrote: > 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 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 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, 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 > >>> > >>> 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 > 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. > Note that > the amount of administrative tasks should be very 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 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 wrote: > >> > >>> I know I'm quite new, but I'm happy to push approved packages.
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 they are approved they can be published. You should have permission to publish the web site already. I will try to verify your changes tomorrow. Ralph > On Sep 1, 2020, at 11:11 PM, Davyd McColl wrote: > > Hi Ralph > > The missing tag is my fault -- I had a `rel/2.0.9` tag locally and obviously > forgot to push 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 updated the README in the project to take out the dormant status > commentary. > > Please review & update the live site if you're happy. > > Previously, as I understand it, the point of the SVN staging area was to > provide built artifacts for the website. Since that's not in play any more, I > was wondering how that's going to happen now? Someone will have to build > before pushing. If you'd like, I could add the target folder that is built > into git so that it's just a matter of copying files. > > I've also added an npm script around building the site, which checks if you > have maven available & builds if possible -- perhaps this makes it easier for > the next new person (: > > -d > > On 2020/09/02 05:20:50, Ralph Goers wrote: > 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 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 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, 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 > >>> > >>> 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 > 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. > Note that > the amount of administrative tasks should be very 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 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 wrote: > >> > >>> 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) > >>> >
