3.1.6 status

3.1.6 status

[Peter Stephenson]

Nothing significant has turned up, so I will probably release 3.1.6 at the
beginning of next week.  If there's a chance 3.0.6 is going to appear at
the same time, I can wait.  I'm going away on 7th August, so a traditional
date would be the 6th August.

Does anyone remember where else the release should be announced apart from
zsh-announce?  comp.unix.shell +...?  I'm assuming there's no point in
posting it to comp.sources.misc any more.

Do we need some overblown hype to go with it?  `The World's Favourite Shell
Just Got Better'?  `Where do you want to go tomorrow'?  I think perhaps
not.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy

Re: 3.1.6 status

[Vin Shelton]

We've had a lot of patches to -test-2.  I would think we should have a
period of no patches before we release 3.1.6.  This period of
stability ensures that we're all running with the same code.  Ideally, 
that period of stability would last several days and no bugs would be
reported against that release.  I would recommend releasing a -test-3
now with all applied patches.  I hope this code would end up being the 
3.1.6 release, but we won't know unless we're all starting from the
same page.

  - vin
-- 
In a minute there is time
For decisions and revisions which a minute will reverse.         T.S. Eliot

Re: 3.1.6 status

[Peter Stephenson]

Vin Shelton wrote:
> We've had a lot of patches to -test-2.  I would think we should have a
> period of no patches before we release 3.1.6.  This period of
> stability ensures that we're all running with the same code.  Ideally, 
> that period of stability would last several days and no bugs would be
> reported against that release.  I would recommend releasing a -test-3
> now with all applied patches.  I hope this code would end up being the 
> 3.1.6 release, but we won't know unless we're all starting from the
> same page.

The trouble is, that's never going to happen.  There are always going to be
patches, and at this stage they're all bug fixes (many of them minor
changes to individual completion functions which I'll accept up to the last
minute, since they're localised).  If I apply them, they fix a bug; if I
don't, then the shell still has a bug.  If I wait until there are none,
I'll wait forever.  That's particularly true of the completion code, for
which there are fiendishly many different things going on; we're never
going to get to a state where last week it was wrong and this week it's
right.

FYI, here are the changes that affect general shell usage and
configuration, excluding completion and documentations changes, which I've
applied since test-2.

	* Sven: 7259, 7261: Src/subst.c, Src/Modules/parameter.c,
	  Doc/Zsh/expn.yo, Completion/Core/_normal,
	  Completion/Core/_parameters: parameter module provides
	  local information; used in _parameters; _normal uses
	  $commands when available.

	* Bart: 7230: Src/exec.c: cancd2 didn't free string properly
	  (or at all, in fact).

	* Sven: 7217: Src/exec.c: duplicate function name for scriptname.

	* Ollivier: 7209, 7210: configure.in, Etc/MACHINES: Elf and a.out
	  dynamic loading on FreeBSD (MACHINES entry adapted).

	* Tanaka Akira: 7205: Src/Modules/mapfile.c: MS_SYNC was not
          defined on SunOS 4.

	* pws: 7202: Src/Modules/clone.c: add an extra zero argument
	  to ioctl() to make three.

Three of those were configuration problems, which only a small number of
users will ever see; one (7259/7261) was a minor addition to the parameters
code; two were simple but necessary local fixes (7217 and 7230).  I'm not
convinced that's enough to let the saga drag on.  But if there's a general
belief, I can hang on another week (and not any apply any patches to the C
code).  Vote now.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy

Hype (was Re: 3.1.6 status)

[Bruce Stephens]

Peter Stephenson <pws@ibmth.df.unipi.it> writes:

> Do we need some overblown hype to go with it?  `The World's Favourite Shell
> Just Got Better'?  `Where do you want to go tomorrow'?  I think perhaps
> not.

`Bringing the bloat to the command line'?  (That's not strictly true,
in that zsh isn't *that* big.  But it *does* have lots of features.)