Another option is to implement this in a hugo native way, without relying
on hosting web server specific redirects. I opened
https://github.com/apache/kafka-site/pull/782 using this approach.

Regards,
Harish


On Fri, Jan 9, 2026 at 4:29 PM tison <[email protected]> wrote:

> About updating templates.py, see
> https://github.com/apache/kafka/pull/21274.
>
> Best,
> tison.
>
>
> Justine Olshan via dev <[email protected]> 于2026年1月10日周六 02:50写道:
>
> > There were a few other instances of longstanding links that changed that
> we
> > were able to make redirects for (see
> > https://github.com/apache/kafka-site/pull/761). But we can also update
> the
> > template going forward. :)
> >
> > Justine
> >
> > On Fri, Jan 9, 2026 at 10:27 AM tison <[email protected]> wrote:
> >
> > > > Should we just update `templates.py`?
> > >
> > > That can also be a follow-up.
> > >
> > > I push [1] because the old link has been spread and keeping it working
> > > is good :D
> > >
> > > [1] https://github.com/apache/kafka-site/pull/779
> > >
> > > Best,
> > > tison.
> > >
> > > Chia-Ping Tsai <[email protected]> 于2026年1月10日周六 02:24写道:
> > > >
> > > > hi all,
> > > >
> > > > Using `https://downloads.apache.org/kafka/KEYS`
> <https://downloads.apache.org/kafka/KEYS>
> > <https://downloads.apache.org/kafka/KEYS>
> > > <https://downloads.apache.org/kafka/KEYS> seems simpler and aligns
> > > > better with Apache policy. Should we just update `templates.py`?
> > > >
> > > > Best,
> > > > Chia-Ping
> > > >
> > > >
> > > > tison <[email protected]> 於 2026年1月10日週六 上午1:49寫道:
> > > >
> > > > > Yes. Here is a patch you can make use of [1]
> > > > >
> > > > > [1] https://github.com/apache/kafka-site/pull/779
> > > > >
> > > > > It also (on the way) put all htaccess rules in the source branch
> > > > > rather than manually updating per staging/production branches.
> > > > >
> > > > > > file a ticket and folks can get on that
> > > > >
> > > > > Sorry I may not have the time to go over the full ticket process.
> The
> > > > > patch is here so if it's a must you can drive the ticket process.
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > > Justine Olshan via dev <[email protected]> 于2026年1月10日周六
> 00:18写道:
> > > > > >
> > > > > > Just to confirm -- we need to fix the site to point to the keys
> > > again? We
> > > > > > can file a ticket and folks can get on that. Thanks!
> > > > > >
> > > > > > Justine
> > > > > >
> > > > > > On Fri, Jan 9, 2026 at 7:39 AM Rich Bowen <[email protected]>
> > > wrote:
> > > > > >
> > > > > > > Thank you! I was able to verify the gpg signatures using that.
> > Much
> > > > > > > appreciated.
> > > > > > >
> > > > > > > —Rich
> > > > > > >
> > > > > > > > On Jan 9, 2026, at 10:33 AM, tison <[email protected]>
> > wrote:
> > > > > > > >
> > > > > > > > It seems there used to be a KEY file [1], but it may have
> been
> > > lost
> > > > > > > > during the website refactor.
> > > > > > > >
> > > > > > > > [1] https://github.com/apache/kafka-site/pull/540
> > > > > > > >
> > > > > > > > If we keep the link https://kafka.apache.org/KEYS, it would
> be
> > > > > better
> > > > > > > > to redirect to [2], according to INFRA guidelines [3].
> > > > > > > >
> > > > > > > > [2] https://downloads.apache.org/kafka/KEYS
> > > > > > > > [3]
> > > > > > >
> > > https://infra.apache.org/release-distribution.html#public-distribution
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > tison.
> > > > > > > >
> > > > > > > > Rich Bowen <[email protected]> 于2026年1月9日周五 23:29写道:
> > > > > > > >>
> > > > > > > >> Hi, folks,
> > > > > > > >>
> > > > > > > >> I was looking back over some recent releases for some
> research
> > > I’m
> > > > > > > doing, and I noticed that in the VOTE thread for 4.1.1. RC2, it
> > > says:
> > > > > > > >>
> > > > > > > >> Kafka's KEYS file containing PGP keys we use to sign the
> > > release:
> > > > > > > >> https://kafka.apache.org/KEYS
> > > > > > > >>
> > > > > > > >> But there is not, in fact, a KEYS file at that location. Can
> > you
> > > > > advise
> > > > > > > please? Thanks.
> > > > > > > >>
> > > > > > > >> —
> > > > > > > >> Rich Bowen
> > > > > > > >> [email protected]
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > >
> > > > > > > —
> > > > > > > Rich Bowen
> > > > > > > [email protected]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
> >
>

Reply via email to