Re: [VOTE] Release Log4Net 2.0.9

2020-09-02 Thread Apache
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

2020-09-02 Thread Davyd McColl
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

2020-09-02 Thread Matt Sicker
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

2020-09-02 Thread Davyd McColl
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