zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@sunsite.dk
Subject: Re: zsh stable release, or is 4.3.4 stable enough for Fedora?
Date: Mon, 11 Jun 2007 23:10:17 +0100	[thread overview]
Message-ID: <200706112210.l5BMAH2T003653@pwslaptop.csr.com> (raw)
In-Reply-To: Message from "Caio Marcelo" <cmarcelo@gmail.com>  of "Mon, 11 Jun 2007 14:03:44 -0300." <d280d7f10706111003y36e619felb328595b64b6955b@mail.gmail.com>

"Caio Marcelo" wrote:
> Hello,
> 
> Is there any plan of releasing a new "stable" release of zsh in the
> near future? Or the stable/unstable convention isn't being used
> anymore?

Strictly speaking, 4.3.4 isn't stable in quite the same way 4.2 is.
How ever, that's less because it's broken than because it's a moving
target; "unstable" means "it keeps changing" rather than "it doesn't
work".  I don't think there are big problems with broken code.

What I'm looking for before producing a new stable release (which will
probably be version 5) are signs that the multibyte support in 4.3 is
complete enough that most users aren't going to find significant gaps.
It doesn't have to be flawless.  At some point we need to decide that
things are working well enough.  With Linux, I think that's already the
case, but I'm less clear about the state of other systems I don't see.

(I've also been worrying about completion inside nested quotes---it's a
fairly minor feature but it's also fairly badly messed up and fixing it
is likely to be a struggle.  I also need to complete the module feature
support; that's not so difficult but will needs some time.)

This doesn't answer the question about when it's going to appear because
I don't yet know.

> I'm asking this because Fedora is holding to update zsh package (today
> it's 4.2.6, from 2005-12-05) because 4.3.x versions are considered
> unstable. On the other hand updating would be very useful because of
> Unicode stuff in newer zsh. Maybe it would be fine to Fedora update to
> 4.3.4? Ubuntu have been using 4.3.x sincfe last year.

On balance, I think most users would probably benefit from upgrading.
The thing to worry about is less stability in terms of bugs, since I
don't see much evidence that's a problem, and more stability in terms of
features; see for example the list of incompatibilities in the README
file.  This isn't going to get much longer before version 5; the biggest
likely one is an option to fix the kludges described in the recent
threads about (R) subscripting (see for example the "Change in FIGNORE
behaviour" thread).

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


  reply	other threads:[~2007-06-11 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmarcelo@gmail.com>
2007-06-11 17:03 ` Caio Marcelo
2007-06-11 22:10   ` Peter Stephenson [this message]
2007-06-11 23:21     ` Caio Marcelo

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=200706112210.l5BMAH2T003653@pwslaptop.csr.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@sunsite.dk \
    /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).