mirror of
git://git.code.sf.net/p/zsh/code
synced 2024-09-27 22:40:20 +02:00
46244 (cont.): Flesh out the TODO from the previous commit.
This commit is contained in:
parent
b9f9a94862
commit
b01e1aec8e
@ -1,5 +1,8 @@
|
||||
2020-07-14 Daniel Shahaf <d.s@daniel.shahaf.name>
|
||||
|
||||
* 46244 (cont.): Etc/creating-a-release.txt: Flesh out the TODO
|
||||
from the previous commit.
|
||||
|
||||
* 46244: Etc/creating-a-release.txt: Start to introduce a
|
||||
release managers keyring.
|
||||
|
||||
|
@ -75,8 +75,9 @@ To create a zsh release:
|
||||
- [one time step] Add your key to the Keys/ directory in the 'web' repository, using
|
||||
`gpg --armor --export $YourPublicKeyFingerprint`.
|
||||
|
||||
TODO: cat Keys/*.asc into a zsh-keyring.asc, upload it along with the
|
||||
tarballs, link to it from Arc/source.html and elsewhere
|
||||
- Create the keyring:
|
||||
|
||||
cat web.git/Keys/*.asc > zsh-keyring.asc
|
||||
|
||||
- Upload to sf.net:
|
||||
|
||||
@ -87,6 +88,22 @@ To create a zsh release:
|
||||
[Select All] next to "Default Download For:". This should cause sf.net
|
||||
to offer that artifact in the "Looking for the latest version?" line.
|
||||
|
||||
You should upload five files:
|
||||
|
||||
zsh-5.8.tar.xz
|
||||
zsh-5.8.tar.xz.asc
|
||||
zsh-doc-5.8.tar.xz
|
||||
zsh-doc-5.8.tar.xz.asc
|
||||
zsh-keyring.asc
|
||||
|
||||
(TODO: what about MD5SUM, FAQ, META-FAQ, all in www.zsh.org/pub/?)
|
||||
|
||||
Note that zsh-keyring.asc is fine to just overwrite, since it's only ever
|
||||
appended to, and in any case the underlying Keys/*.asc files are in version
|
||||
control.
|
||||
|
||||
TODO: link to zsh-keyring.asc from Arc/source.html and elsewhere
|
||||
|
||||
- If the new release is a stable release, update zsh.sf.net:
|
||||
|
||||
# Move into the 'web' repository mentioned above
|
||||
|
Loading…
Reference in New Issue
Block a user