From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>, zsh-workers@zsh.org
Subject: Re: zsh download links
Date: Fri, 28 Sep 2018 14:38:14 +0000 [thread overview]
Message-ID: <1538145494.3996501.1523942616.6808E06E@webmail.messagingengine.com> (raw)
In-Reply-To: <A345516C-BFB8-450F-86D3-AE9E66A818E2@kba.biglobe.ne.jp>
Jun T wrote on Fri, 28 Sep 2018 21:01 +0900:
> Links in
> (1) http://zsh.sourceforge.net/Arc/source.html
> still point to zsh-5.5.1, and the last entry in http://zsh.sourceforge.net/News/
> is also 5.5.1.
>
Fixed. It may take a few minutes for sourceforge's caches to pick it up.
Could I ask for someone to (1) add this to Etc/creating-a-release.txt,
(2) write a script for updating that page that can be run as part of the
release process? I've got my hands full. (The web pages are in git;
creating-a-release.txt has a pointer.)
> If a user starts from the top page
> (2) http://zsh.sourceforge.net
> it would be quite difficult to find the SourceForge's download page
> (3) https://sourceforge.net/projects/zsh/files/
> or the download page in zsh.org
> (4) http://www.zsh.org/pub/
>
I agree. The Web pages are in git. They're straight html (not
generated from anything). Would you have time to patch this?
> It seems the only way to reach (3) from (2) is via the link at the
> bottom of (1), "Older releases can be downloaded from the zsh
> downloads on Sourceforge", and I can't find any page that has a
> link to (4).
>
> Even if a user finds the page (3), the "Download Latest Version" link
> on the page points to 5.6.1, not 5.6.2.
Fixed. It may take a few minutes for sourceforge's caches to pick it
up. I must have overlooked this last time, sorry.
Cheers,
Daniel
prev parent reply other threads:[~2018-09-28 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 12:01 Jun T
2018-09-28 14:38 ` Daniel Shahaf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1538145494.3996501.1523942616.6808E06E@webmail.messagingengine.com \
--to=d.s@daniel.shahaf.name \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).