[PATCH][DRAFT] Release 5.6.2

[PATCH][DRAFT] Release 5.6.2

[Daniel Shahaf]

---
To be clear, this is just a draft.

Daniel

 Config/version.mk |  4 ++--
 Etc/FAQ.yo        |  2 +-
 NEWS              | 11 +++++++++++
 README            |  5 +++--
 4 files changed, 17 insertions(+), 5 deletions(-)

diff --git a/Config/version.mk b/Config/version.mk
index 8e48bc5c8..33ce37195 100644
--- a/Config/version.mk
+++ b/Config/version.mk
@@ -27,5 +27,5 @@
 # This must also serve as a shell script, so do not add spaces around the
 # `=' signs.
 
-VERSION=5.6.1-dev-0
-VERSION_DATE='September 8, 2018'
+VERSION=5.6.2
+VERSION_DATE='September 14, 2018'
diff --git a/Etc/FAQ.yo b/Etc/FAQ.yo
index 10c773b75..a3dfc6c13 100644
--- a/Etc/FAQ.yo
+++ b/Etc/FAQ.yo
@@ -306,7 +306,7 @@ sect(On what machines will it run?)
 
 sect(What's the latest version?)
 
-  Zsh 5.6.1 is the latest production version.  For details of all the
+  Zsh 5.6.2 is the latest production version.  For details of all the
   changes, see the NEWS file in the source distribution.
 
   A beta of the next version is sometimes available.  Development of zsh is
diff --git a/NEWS b/NEWS
index 7c7d64c72..f3e617b9c 100644
--- a/NEWS
+++ b/NEWS
@@ -4,6 +4,17 @@ CHANGES FROM PREVIOUS VERSIONS OF ZSH
 
 Note also the list of incompatibilities in the README file.
 
+Changes from 5.6.1 to 5.6.2
+---------------------------
+
+Fix another SIGTTOU case.
+
+Fix SIGWINCH being ignored when zsh is not in the foreground.
+
+The release tarballs are now compressed using xz(1), whereas previously
+both xz(1) and gzip(1) versions were available.  If this gets in your way,
+give us a shout.
+
 Changes from 5.6 to 5.6.1
 -------------------------
 
diff --git a/README b/README
index c9a4ed693..c792d4075 100644
--- a/README
+++ b/README
@@ -5,8 +5,9 @@ THE Z SHELL (ZSH)
 Version
 -------
 
-This is version 5.6.1 of the shell.  This is a bugfix release, following
-5.6 which was a security and feature release.
+This is version 5.6.2 of the shell.  This is a bugfix release, following
+5.6 which was a security and feature release and 5.6.1 which was a bugfix
+release.
 
 Note in particular the changes highlighted under "Incompatibilities since
 5.5.1" below.  See NEWS for more information.

Re: [PATCH][DRAFT] Release 5.6.2

[Bart Schaefer]

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

On Wed, Sep 12, 2018, 8:10 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:

> ---
> To be clear, this is just a draft.
>

Perhaps we should be doing a -test-1 tag etc.?  Lot of stuff popping up
right after release these past few times.


>

Re: [PATCH][DRAFT] Release 5.6.2

[Daniel Shahaf]

Bart Schaefer wrote on Wed, 12 Sep 2018 08:13 -0700:
> On Wed, Sep 12, 2018, 8:10 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> 
> > ---
> > To be clear, this is just a draft.
> >
> 
> Perhaps we should be doing a -test-1 tag etc.?  Lot of stuff popping up
> right after release these past few times.

We did do a 5.5.1-test-1 tag before 5.6.  I'm not sure doing 5.6.1-test-1
tag before 5.6.2 would help: anyone who'd test such a tag can just as
easily test 5.6.1 + (patches cherry-picked from git), can't they?

Cheers,

Daniel

Re: [PATCH][DRAFT] Release 5.6.2

[Bart Schaefer]

[-- Attachment #1: Type: text/plain, Size: 394 bytes --]

On Wed, Sep 12, 2018, 8:18 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:

>
> We did do a 5.5.1-test-1 tag before 5.6.  I'm not sure doing 5.6.1-test-1
> tag before 5.6.2 would help: anyone who'd test such a tag can just as
> easily test 5.6.1 + (patches cherry-picked from git), can't they?
>


I don't know that everyone who has been reporting these issues actually
uses git checkouts.

>

Re: [PATCH][DRAFT] Release 5.6.2

[Daniel Shahaf]

Bart Schaefer wrote on Wed, 12 Sep 2018 09:32 -0700:
> On Wed, Sep 12, 2018, 8:18 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> 
> >
> > We did do a 5.5.1-test-1 tag before 5.6.  I'm not sure doing 5.6.1-test-1
> > tag before 5.6.2 would help: anyone who'd test such a tag can just as
> > easily test 5.6.1 + (patches cherry-picked from git), can't they?
> >
> 
> 
> I don't know that everyone who has been reporting these issues actually
> uses git checkouts.

I meant, they could pick the patches from -workers@ (or from git, for
that matter) and apply them to their extracted 5.6.1 tarballs.  This is
how they would be able to test the patches without having to have the
Util/preconfig prerequisites installed.

But it wouldn't take _that_ long to produce a 5.6.1-test-1, either...

Cheers,

Daniel