Hi
On Mon, Oct 23, 2023, at 11:01, Volkan Yazıcı wrote:
> Staging website has been broken since October 10, that is, the last two
> weeks – please, correct me if I'm wrong. I support Christian's Jekyll
> migration and I know he is blocked by INFRA.
I have created the issue only 5 days ago, after
Staging website has been broken since October 10, that is, the last two
weeks – please, correct me if I'm wrong. I support Christian's Jekyll
migration and I know he is blocked by INFRA.
1. Do we have a deadline to consider alternative courses of action?
2. Can we implement your Jekyll goal
Hi Stephen,
On Wed, 18 Oct 2023 at 07:36, Stephen Webb wrote:
>
> Hi Piotr,
>
> The Log4cxx staging website URL
> https://logging.staged.apache.org/log4cxx/latest_stable/usage-overview.html
> now reports a 404.
>
> The .asf.yaml contains:
>
> staging:
> profile: ~
> whoami: asf-staging
>
Hi Piotr,
The Log4cxx staging website URL
https://logging.staged.apache.org/log4cxx/latest_stable/usage-overview.html
now reports a 404.
The .asf.yaml contains:
staging:
profile: ~
whoami: asf-staging
subdir: content/log4cxx
Do you have a suggestion as to where I can find it now?
Nevermind. I was using the wrong url.
Ralph
> On Oct 13, 2023, at 8:21 AM, Ralph Goers wrote:
>
> I get a 404 trying to access the log4j2 staging web site. Although
> technically not required for a release I am not comfortable voting for the
> release without being able to see the web site.
I get a 404 trying to access the log4j2 staging web site. Although technically
not required for a release I am not comfortable voting for the release without
being able to see the web site.
Ralph
> On Oct 13, 2023, at 6:46 AM, Piotr P. Karwasz wrote:
>
> Hi Christian,
>
> On Fri, 13 Oct
Hi Christian,
On Fri, 13 Oct 2023 at 13:46, Christian Grobmeier wrote:
> Why is content not causing this issue?
> For me both is possible, just trying to understand the best way.
>From what I understand, if a branch (in any repo) has a configuration:
staging:
whoami: name_of_the_branch
>> [1] Christian's recent Jekyll experiment on the `asf-staging` branch
>> of `logging-site` repository confused the INFRA and it is acting
>> strangely. This will *NOT* be an issue when we push the website
>> changes to production, i.e., `asf-site` branch. Though we will try
>> fixing
