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 <dav...@gmail.com> wrote:
> 
> 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 and validated that the *2.0.9* links point at the right 
> place; pushed to asf-staging & checked on 
> http://logging.staged.apache.org/log4net.
> 
> -d
> On 2020/09/05 08:12:19, Ralph Goers <ralph.go...@dslextreme.com> wrote:
> 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 variable in 
> the pom.xml file.
> 
> Ralph
> 
> 
>> On Sep 2, 2020, at 11:01 PM, 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 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).
>> 
> 
> 


Reply via email to