Hi,

This is very odd, indeed.

The jenkins job ran on December 15th to publish a new site
https://builds.apache.org/job/BigTop/job/pipeline-site/71/ 
<https://builds.apache.org/job/BigTop/job/pipeline-site/71/>

The log in asf-site branch shows this timing as well
https://gitbox.apache.org/repos/asf?p=bigtop.git;a=shortlog;h=refs/heads/asf-site
 
<https://gitbox.apache.org/repos/asf?p=bigtop.git;a=shortlog;h=refs/heads/asf-site>

However something has reverted back the site.

We need to ask INFRA what is going on.
https://issues.apache.org/jira/browse/INFRA-21413

Best,
     Olaf



> Am 10.02.2021 um 10:20 schrieb Konstantin Boudnik <[email protected]>:
> 
> And there's a ticket for this BIGTOP-3496
> 
> --
> With regards,
>  Cos
> 
> On 10.02.2021 12:17, Konstantin Boudnik wrote:
>> In the old times when the website was living in the SVN, there was an 
>> additional step to publish the changes to the public stage.
>> However, I am looking at the site right now and I see this time stamps:
>> Last Published: 2020-04-18
>> Which explains 1.4.0
>> I wonder if this is somehow connected to the recent switch to git-based 
>> publishing?
>> -- 
>> With regards,
>>   Cos
>> On 10.02.2021 11:12, Kengo Seki wrote:
>>> Thank you for the notification, Cos!
>>> Hmm, that sounds strange. I made sure the website was correctly
>>> updated when releasing 1.5.0. I took screenshots and pasted them into
>>> my blog which introduces 1.5.0 in Japanese.
>>> https://sekikn.github.io/blog/2020/12/19/introducing-bigtop-1.5.0-1.html
>>> https://sekikn.github.io/blog/2020/12/20/introducing-bigtop-1.5.0-2.html
>>> 
>>> I'm going to investigate its cause this weekend at the latest.
>>> 
>>> Kengo Seki <[email protected]>
>>> 
>>> On Tue, Feb 9, 2021 at 3:11 PM Konstantin Boudnik <[email protected]> wrote:
>>>> 
>>>> Fellas,
>>>> 
>>>> just noticed that our website wasn't updated as a part of 1.5 release. I
>>>> presume the release manager did miss a step, perhaps? ;)
>>>> 
>>>> Please let me know if any help is needed!
>>>> 
>>>> -- 
>>>> With regards,
>>>>     Cos

Reply via email to