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 update
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
For what it's worth, GitHub Pages is simply a Jekyll-based site. If
you want something convenient like that, I highly recommend doing
something like Apache Accumulo and Apache Fluo did, to take advantage
of the ASF infrastructure, rather than rely on GitHub Pages to
generate the Jekyll.
See the Je
All the sites should now be online.
Ralph
> On Sep 1, 2020, at 8:57 AM, Christian Grobmeier wrote:
>
> Hi,
>
> I see there is some activity on the site - I discovered log4php and the audit
> component are currently 404.
> the links look correct, it seems as the sites are not at their location
FWIW, this change won’t have any effect as I asked infra to decommission the
CMS-based web site. You need to make the modifications in the GitHub repo.
Ralph
> On Aug 31, 2020, at 11:16 PM, dav...@apache.org wrote:
>
> Author: davydm
> Date: Tue Sep 1 06:16:14 2020
> New Revision: 1065013
>
>
Apache doesn’t support using GitHub pages for the live site. They do allow it
to be used for the staging site, but the details of how they work aren’t the
same. To define a GitHub Pages site you have to specify
github:
ghp_branch: master
ghp_path:/docs
where the ghp_path has to be eith
Hi,
I see there is some activity on the site - I discovered log4php and the audit
component are currently 404.
the links look correct, it seems as the sites are not at their location.
Christian
On Tue, Sep 1, 2020, at 03:24, Robert Middleton wrote:
> Something is funny with logging.apache.org -
You can make direct links to the file on downloads.a.o nowadays as that's
the expected method. The mirror select is now a backend detail of the
download site itself.
On Tue, 1 Sep 2020 at 10:04, Davyd McColl wrote:
> Matt
> I don't mind doing so - I'd just have to update the base download html
>
Part of it is because Apache offers an equivalent service for
publishing sites to apache.org directly rather than to github.io.
On Tue, 1 Sep 2020 at 09:21, Volkan Yazıcı wrote:
>
> Ralph, regarding your "after a discussion on Slack with infra I determined
> that using GitHub pages isn’t what we
Matt
I don't mind doing so - I'd just have to update the base download html file, if
that's ok (and the download link on the main page as it points to the .cgi).
Most of the download page exists "as-is", but I can see that there's
placeholders for selecting mirrors. If I can simply replace thos
You can link directly to
https://downloads.apache.org/ as that site handles mirror redirects or CDN
or whatever it’s implemented as right now. That CGI script is ancient and
is no longer necessary as of, oh, many years I think? 😉
On Tue, Sep 1, 2020 at 01:17 Davyd McColl wrote:
> Ralph, the log4
Ralph, regarding your "after a discussion on Slack with infra I determined
that using GitHub pages isn’t what we want to do." remark... I am curious
to know about the details. Can we use GitHub pages in some way? Or why one
should prefer one over another?
On Mon, Aug 31, 2020 at 7:21 AM Ralph Goer
12 matches
Mail list logo
