From: dana <dana@dana.is>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh Workers List <zsh-workers@zsh.org>
Subject: Re: Test release: 5.7.1-test-1
Date: Fri, 20 Dec 2019 15:26:09 -0600 [thread overview]
Message-ID: <F84AFABE-7AF9-4C2B-B68D-9D9D8F6BAA46@dana.is> (raw)
In-Reply-To: <20191217011646.cznpheompwvpmwi6@tarpaulin.shahaf.local2>
On 16 Dec 2019, at 19:16, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> I'd say, go ahead with making the change unless anyone objects. It won't
> affect the numbering of stable releases so the risk of disruption is minimal.
OK, sorry, needed to let this sit for a while.
I've updated the versioning scheme per your suggestion (as i interpreted it,
at least). I also updated the example versions so it's not quite *as*
ahistorical. This is what you had in mind, right?
If there are no further issues, i will probably post another test release this
week end (per workers/45047). I'm going to stick with the current versioning
scheme until 5.8 is out, so as not to mess up any version comparisons between
5.7.x releases.
dana
diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt
index dfde269ae..485d7ebaf 100644
--- a/Etc/creating-a-release.txt
+++ b/Etc/creating-a-release.txt
@@ -6,37 +6,55 @@ To create a zsh release:
- Bump or update:
Config/version.mk to today's date
- Config/version.mk version number (sequence: 5.4.2, 5.4.2-dev-$((i++)), 5.4.2-test-$((++j)), 5.5)
+ Config/version.mk version number
Etc/FAQ.yo
README
NEWS
+ The version-number sequence is as follows:
+
+ 5.8, 5.8.0.1-dev, 5.8.0.2-test, 5.8.1, 5.8.1.1-dev, 5.8.1.2-test, 5.9
+
+ Please note:
+
+ - All version numbers in this document are examples only and may not
+ reflect the actual version history of the shell.
+ - A slightly different ordering of version-number components was used
+ prior to zsh 5.8. All subsequent releases should use the scheme
+ described above.
+ - Usually there is only one -dev version (1-dev), but there may be more
+ if for example there is a wordcode compatibility break, in which case
+ the sequence would be something like 1-dev, 2-dev, 3-test, ....
+
README should document compatibility-breaking changes. Generally, NEWS should
document new features and major bug fixes (but not routine fixes or changes to
completion/contrib functions).
+ For -test releases, you may update the FAQ, README, etc., to refer to the
+ upcoming stable version number.
+
- Commit those changes with an "unposted" ChangeLog entry.
- git commit -am "Test release: 5.5.1-test-1." &&
+ git commit -am "Test release: 5.8.1.2-test." &&
zshdev-add-nnnnn-and-changelog unposted
# (Everyone has a different way of getting the "unposted" magic string
# into ChangeLog and the log message. This script is how I do it; YMMV;
# see Etc/zsh-development-guide for alternative scripts.)
-- Create signed git tag named "zsh-5.5.1-..." (not "5.5.1-...")
+- Create signed git tag named "zsh-5.8.1..." (not "5.8.1...")
- git tag --sign -m "Tag version zsh-5.5.1-test-1." zsh-5.5.1-test-1
+ git tag --sign -m "Tag version zsh-5.8.1.2-test." zsh-5.8.1.2-test
- If the tagged release is a stable release (as opposed to a test release):
- vi Config/version.mk # bump to 5.6-dev-0 and tomorrow's date
+ vi Config/version.mk # bump to 5.9.0.1-dev and tomorrow's date
git commit -am "Post-release version bump." &&
zshdev-add-nnnnn-and-changelog unposted
# or local equivalent (see above)
- Create tarball:
- git checkout zsh-5.5.1-test-1
+ git checkout zsh-5.8.1.2-test
git diff HEAD # ensure no local mods
rm -f Doc/help.txt Doc/help/[_a-zA-Z0-9]* # some devs have had issues with these
Util/preconfig && ./configure ...
@@ -50,11 +68,11 @@ To create a zsh release:
git clone git://git.code.sf.net/p/zsh/web
git clone ssh://git.code.sf.net/p/zsh/web
-- Upload to sf.net
+- Upload to sf.net:
Test releases go to the "zsh-test" directory.
Stable releases to zsh/ and zsh-doc/.
- After uploading, select the tar.xz artifact, press the 🛈 button ("View Details") to its right, and press [Select All] next to "Default Download For:". This should cause sf.net to offer that artifact in the "Looking for the latest version?" line.
+ For stable releases only, after uploading, select the tar.xz artifact under zsh/, press the 🛈 button ("View Details") to its right, and press [Select All] next to "Default Download For:". This should cause sf.net to offer that artifact in the "Looking for the latest version?" line.
- If the new release is a stable release, update zsh.sf.net:
@@ -94,7 +112,7 @@ To create a zsh release:
# several minutes to appear afterwards
rsync ...
-- Upload the build artefacts to zsh.org/pub; you may need assistance from
+- For stable releases, upload the build artefacts to zsh.org/pub; you may need assistance from
another dev if you don't have access to do this.
- Post to -workers@
diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt
index 485d7ebaf..27a5b9a5a 100644
--- a/Etc/creating-a-release.txt
+++ b/Etc/creating-a-release.txt
@@ -63,7 +63,8 @@ To create a zsh release:
make tarxz-doc tarxz-src
for i in zsh*.tar.?z ; do gpg -ab -- $i ; done
-- [one time step] Add your key to http://zsh.sf.net/Arc/source.html; see README in the 'web' repository for how to do this. Its URL is:
+- [one time step] Add your key to http://zsh.sf.net/Arc/source.html; see README
+ in the 'web' repository for how to do this. Its URL is:
git clone git://git.code.sf.net/p/zsh/web
git clone ssh://git.code.sf.net/p/zsh/web
@@ -72,7 +73,10 @@ To create a zsh release:
Test releases go to the "zsh-test" directory.
Stable releases to zsh/ and zsh-doc/.
- For stable releases only, after uploading, select the tar.xz artifact under zsh/, press the 🛈 button ("View Details") to its right, and press [Select All] next to "Default Download For:". This should cause sf.net to offer that artifact in the "Looking for the latest version?" line.
+ For stable releases only, after uploading, select the tar.xz artifact
+ under zsh/, press the 🛈 button ("View Details") to its right, and press
+ [Select All] next to "Default Download For:". This should cause sf.net
+ to offer that artifact in the "Looking for the latest version?" line.
- If the new release is a stable release, update zsh.sf.net:
@@ -112,8 +116,8 @@ To create a zsh release:
# several minutes to appear afterwards
rsync ...
-- For stable releases, upload the build artefacts to zsh.org/pub; you may need assistance from
- another dev if you don't have access to do this.
+- For stable releases, upload the build artefacts to zsh.org/pub; you may need
+ assistance from another dev if you don't have access to do this.
- Post to -workers@
next prev parent reply other threads:[~2019-12-20 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 19:20 dana
2019-12-15 3:58 ` Daniel Shahaf
2019-12-15 4:32 ` dana
2019-12-15 5:16 ` Daniel Shahaf
2019-12-15 5:50 ` dana
2019-12-15 18:28 ` Peter Stephenson
2019-12-16 3:55 ` Daniel Shahaf
2019-12-16 22:11 ` dana
2019-12-17 1:16 ` Daniel Shahaf
2019-12-20 21:26 ` dana [this message]
2019-12-21 8:13 ` Daniel Shahaf
2019-12-16 1:21 ` dana
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=F84AFABE-7AF9-4C2B-B68D-9D9D8F6BAA46@dana.is \
--to=dana@dana.is \
--cc=d.s@daniel.shahaf.name \
--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).