zsh-workers
 help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: "Zsh hackers list" <zsh-workers@zsh.org>
Subject: Posted zsh 5.9
Date: Sat, 14 May 2022 15:59:35 -0500	[thread overview]
Message-ID: <25ece9e8-71fb-4cf4-adf1-1fbef7eda0a1@www.fastmail.com> (raw)

I've just finished posting zsh 5.9. It should be available in the usual
places:

  https://sourceforge.net/projects/zsh/files/
  https://www.zsh.org/pub/

With the notes at:

  https://zsh.sourceforge.io/releases.html

creating-a-release instructs us to wait a day before posting to -announce,
which has always been followed a little loosely i think, at least by me...
but i'll do that this time, unless someone wants me to go ahead now.

Some things i noted this time around:

* creating-a-release doesn't explicitly say where to put the zsh-keyring
  file for stable releases. (It's obvious for test releases since there's
  only one place it could go.) I guess for that reason i did not upload it
  to SF when i posted 5.8.1. This time i put it under zsh/ (and not
  zsh-doc/). Is that the intention?

* The release-update-versions script in the web repo failed to complete
  because, despite being passed the --content-disposition option, wget was
  not fully respecting the attachment name for the files it downloaded from
  SF, resulting in the addition of query-string parameters to the ends of
  the file names. I hacked around this by making the script do a rename
  pass after the wget, not sure if we want to come up with something nicer.
  (`curl -LJO` names the files correctly, fwiw)

* This has probably been discussed before, but is it deliberate that the
  (roff-formatted) man pages are in the source archive and not in the doc
  one? The Homebrew package maintainers don't seem to be aware of this (they
  only pull the HTML files from the doc archive), and i wanted to confirm
  that that's how it's meant to be before i submit a PR

dana


             reply	other threads:[~2022-05-14 21:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 20:59 dana [this message]
2022-05-14 21:50 ` Daniel Shahaf
2022-05-14 21:58   ` Daniel Shahaf
2022-05-14 22:27   ` dana
2022-05-14 23:26     ` Daniel Shahaf
2022-05-14 23:28     ` Daniel Shahaf
2022-05-14 23:50       ` dana
2022-05-15 10:36         ` Daniel Shahaf
2022-05-15 21:43           ` dana
2022-05-16 23:57   ` Phil Pennock
2022-05-21  1:31     ` Daniel Shahaf
2022-05-14 22:11 ` Axel Beckert
2022-05-14 22:31   ` dana
2022-05-15  4:33     ` Bart Schaefer
2022-05-15  6:00       ` dana
2022-05-14 23:21   ` Daniel Shahaf
2022-05-14 23:35     ` Axel Beckert
2022-05-14 23:49       ` Daniel Shahaf

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=25ece9e8-71fb-4cf4-adf1-1fbef7eda0a1@www.fastmail.com \
    --to=dana@dana.is \
    --cc=zsh-workers@zsh.org \
    --subject='Re: Posted zsh 5.9' \
    /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

Code repositories for project(s) associated with this 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).